Changelog

Managed custom domains

Endpoints can now use a custom domain with a certificate Alien issues and renews, while the customer keeps their own DNS:

alien domains add api.customer-1.example --dns customer
alien deployments set-domains customer-1/us-east-1 --resource api \
  --endpoint default=api.customer-1.example

alien domains add prints the DNS records to create: an _acme-challenge CNAME that lets Alien prove control of the name, and a CNAME that points traffic at the deployment. Once the records exist, the domain verifies, and the certificate is issued and renewed with no further steps.

With --dns alien, the zone is delegated to Alien and the records are created for you. --clear returns an endpoint to its generated domain.

  • Uninterrupted renewal: the last issued certificate keeps serving until its replacement is ready
  • Second certificate authority: issuance fails over to another ACME provider
  • Customer-supplied certificates: an ACM, Certificate Manager, Key Vault, or TLS Secret certificate still works, and Alien never sees the private key
  • Domains in the dashboard: a verified domain can be offered to a project from its settings

Read the docs →