Custom CNAME or proxy support for balenaOS --> balenaCloud?

Is it possible to configure balenaOS to use a custom CNAME or a proxy for all communications to Balena Cloud? When we deploy gateways in customer environments everyone’s life would be a lot easier if we can tell the customer we only do outbound https (TCP/443) to * rather than * + * + etc… For Mender and Datadog we host a proxy in Cloudflare, but Balena’s VPN model makes this quite a bit more difficult.

I just found Network Setup on balenaOS - Balena Documentation … I will give this a go. Hopefully there is a way to do mtls auth on the proxy instead of username/password auth.

1 Like

Thanks @scscsc for sharing the solution that you are going to test. Let us know if that works.