Amazon’s authority, behind every public certificate from AWS Certificate Manager — on CloudFront, load balancers and API Gateway. Any one of its names in a CAA record lets it issue; amazon.com is the usual one.
| Run by | Amazon Trust Services, United States |
| CAA value | amazon.com — it also accepts amazontrust., awstrust., amazonaws., amazontrustservices., amazonaws., amznts. |
| CAA parameters | Not documented |
| Cost | Through AWS Certificate Manager, for AWS services |
| Certificates | Domain validated (DV) only; wildcards |
| Longest certificate | 198 days |
| Issuer names on its certificates | Amazon RSA 2048 M01–M06, Amazon ECDSA 256 M01–M06, Amazon RSA 2048 S06–S25 |
| Issues for | AWS Certificate Manager: CloudFront, Elastic Load Balancing, API Gateway |
May Amazon Trust Services issue for your domain?
Enter a domain or hostname: we read its CAA records as Amazon Trust Services must — its own, or the nearest parent’s — and say whether they let it issue, for wildcards too, and which authority issued the certificate it serves now.
The CAA record for Amazon Trust Services
Published on your domain, this lets Amazon Trust Services issue for it and for every name under it that has no CAA records of its own. Every authority not named must refuse. Keep the records for any other authority you use — your host’s or CDN’s included.
example.com. CAA 0 issue "amazon.com"
An issue record covers wildcard certificates too. To let Amazon Trust Services issue wildcards and no one else, add an issuewild record — once there is one, issue records stop counting for wildcards — and an iodef address for authorities to report refused requests to:
example.com. CAA 0 issuewild "amazon.com"
example.com. CAA 0 iodef "mailto:security@example.com"
How it reads CAA
ACM documents four values — amazon.com, amazontrust.com, awstrust.com, amazonaws.com; its policy accepts three .eu names too, and names under them such as aws.amazon.com. With no issuewild record, an issue record for Amazon covers ACM’s wildcards; an issuewild record that leaves Amazon out stops them. ACM ignores iodef.
Getting a certificate
Request it in AWS Certificate Manager for use on AWS services; since 2026 ACM also has ACME endpoints, with an external account key tied to an IAM role.
When a CAA record stops it
ACM shows “One or more domain names have failed validation due to a Certification Authority Authorization (CAA) error”, with the failure reason CAA_ERROR.
What changed
- 11 October 2022 — Dynamic intermediates: ACM picks one at random, and may retire it without notice.
- 27 November 2025 — Added three .eu names to the CAA values it accepts.
- 6 August 2026 — Announced ACME support in ACM.
Worth knowing
- DigiCert accepts Amazon’s four .com names too, and operates some of Amazon’s older intermediates: a record naming amazon.com lets DigiCert issue as well.
- ACM does not tell you which intermediate a certificate will get, so do not pin one.
Questions
Which CAA record does AWS Certificate Manager need?
Any one of 0 issue “amazon.com”, “amazontrust.com”, “awstrust.com” or “amazonaws.com” — and, if the domain has issuewild records, one of them in issuewild too for a wildcard.
Sources
Checked on 27 September 2026 against these official sources:
- Ats cp cps 2.7 — amazontrust.com
- Set up to use AWS Certificate Manager — docs.aws.amazon.com
- Certification Authority Authorization (CAA) problems — docs.aws.amazon.com
- AWS Certificate Manager public certificate characteristics and limitations — docs.aws.amazon.com