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
| Parameter | Type | Required | Description |
|---|---|---|---|
org_id | string | Yes | Clerk organization slug |
Example Request
Example Response
Response Fields
| Field | Type | Description |
|---|---|---|
txt_record_name | string | DNS TXT record name to add |
txt_record_value | string | DNS TXT record value |
order_url | string | ACME order URL (for tracking) |
authorization_url | string | ACME authorization URL |
challenge_url | string | ACME challenge URL |
finalize_url | string | ACME finalize URL |
What Happens Next
- User adds the TXT record via Entri
- Frontend calls
/complete-certificateto validate and issue the cert - Certificate is imported to ACM and attached to CloudFront
- User can then switch their www CNAME to CloudFront (zero downtime!)