Domains

{/* Imported from CoderHelm/coderhelm-platform/docs/self-host/domains.md at 96a2a3bafd5e. Edit it there. */} CoderHelm serves the dashboard, the API and the chat stream from one hostname through one CloudFront distribution:

One hostname keeps the session cookie first-party and removes the need for CORS.

No domainCopy Anchor Link

"domain": null

CloudFront gives you a URL like https://d1234abcd.cloudfront.net. It is only known after the first deploy, so the web stack writes it to SSM (/coderhelm-<stage>/public-url), and the services read it there when they start. Everything works, including the GitHub App; Google sign-in needs a domain.

A domain in Route 53Copy Anchor Link

"domain": { "hostname": "coderhelm.example.com", "hostedZone": "example.com" }

The deploy creates the certificate (validated by DNS) and the A and AAAA alias records. CloudFront only uses certificates from us-east-1; in any other region the deploy adds a small stack there for the certificate, and the installer bootstraps CDK in us-east-1 too.

A domain anywhere elseCopy Anchor Link

1. In ACM in us-east-1, request a certificate for the hostname and add the validation CNAME at your DNS provider.
2. Set:

   Copy Text

   "domain": {
     "hostname": "coderhelm.example.com",
     "certificateArn": "arn:aws:acm:us-east-1:123456789012:certificate/..."
   }

3. Deploy. The output DnsRecord gives the CNAME to create (coderhelm.example.com CNAME dxxxx.cloudfront.net).

Changing the domain laterCopy Anchor Link

Deploy with the new domain, then update the GitHub App's URLs (see The GitHub App) and, if you use them, the Jira webhook and the Google OAuth client.