Skip to main content
Start a Let’s Encrypt certificate request for a domain. This is Step 1 of the zero-downtime domain connection flow. Returns a TXT record that the user must add to their DNS to verify domain ownership.

Why Let’s Encrypt?

We use Let’s Encrypt instead of Amazon ACM because:
  • Universal compatibility: Let’s Encrypt is allowed by ALL DNS providers
  • No CAA conflicts: Some providers (Vercel, Netlify) have CAA records that block Amazon
  • Fast issuance: Certificates are issued in seconds after DNS verification

Path Parameters

Example Request

Example Response

Response Fields

What Happens Next

  1. User adds the TXT record via Entri
  2. Frontend calls /complete-certificate to validate and issue the cert
  3. Certificate is imported to ACM and attached to CloudFront
  4. User can then switch their www CNAME to CloudFront (zero downtime!)

Frontend Integration