Already have an ingress controller? Give the installer a
--domain (or set ingress.enabled=true in Helm values) and skip to DNS records.Option A: VPN or corporate network access
If your organization has a VPN that routes into the VPC, users can access xpander services directly: no ingress controller, NLB, ACM certificate, or public DNS needed. Point internal DNS records to the Kubernetes services:Option B: Public access via ingress + NLB
For public or internet-facing access, set up an ACM certificate, an nginx ingress controller, and an NLB, using the three steps below: SSL Certificate, Ingress Controller, and DNS Records.SSL certificate
Request an ACM certificate for your domain.<DOMAIN> and *.<DOMAIN> share one validation record:
Ingress controller
Install the nginx ingress controller with AWS NLB and ACM SSL termination:DNS records
Create a wildcard CNAME record pointing*.<DOMAIN> to the NLB hostname.
ingress.domainStyle.mode: dash, each host is <service>-<DOMAIN> instead):
MCP clients sign in through the API host (
API_URL), and the MCP host is the install’s MCP address (MCP_SERVICE_URL). Since chart 0.22.9 both are https:// and follow ingress.domainStyle.mode, also when TLS ends at the load balancer (ingress.tls.enabled: false). An api.env.API_URL you set still wins.
Test it:

