ACM manages public and private certificates for integrated AWS endpoints and supports exports for other hosts. Choose the trust model, validation method, and certificate Region first, then follow the renewal and deployment lifecycle for that certificate.
Public certificates and domain validation
ACM issues and manages certificates for TLSTLS authenticates a server and encrypts communication between a client and server., the protocol that authenticates servers and encrypts client-server traffic. A certificateA certificate binds an identity to a public key using a digital signature. binds an identity to a public keyA public key is the shareable half of an asymmetric key pair and can be included in a certificate.. A certificate authorityA certificate authority signs certificates that bind an identity to a public key. (CA) signs that binding so clients can decide whether to trust it.
How it works
- Choose the certificate type. Public certificates suit public endpoints; private certificates rely on a root CA trusted by your clients. A trust storeA trust store is the collection of CA certificates a client accepts as trusted. is the client’s collection of trusted CA certificates.
- For an ACM-issued public certificate, prove control of every requested domain. With DNSDNS is the directory system that holds records for names in a domain., the directory of domain records, publish the CNAMEA CNAME record points one DNS name to another and can carry ACM domain-control proof. record supplied by ACM. A CNAME points one DNS name to another. The record must be in public DNS, not a private hosted zoneA hosted zone is a container of DNS records for a domain and its subdomains..
- Wait for issuance, then attach the certificate to the integrated endpoint. Request it in the Region required by that endpoint.
- Keep validation records in place for later renewal. The DNS token can support requests for the same domain across Regions, but each certificate remains a separate Regional resource.
| Certificate type | Trust | Use |
|---|---|---|
| Public | Major browsers and operating systems trust it. | Public endpoints such as an ALB. |
| Private | Clients must trust your root CA. | Internal services using ACM with AWS Private CA. |
| Imported | Supplied from outside ACM. | An existing certificate for an integrated serviceAn integrated service can use an ACM certificate directly for its endpoint.. |
| Validation method | Required proof | Scope |
|---|---|---|
| DNS | Publish the ACM CNAME. | Public domains, including wildcard requests. |
| Approve the validation email. | Legacy workflows being phased out during 2027. |
| Endpoint | Certificate Region |
|---|---|
| ALB | Same Region as the load balancer. |
| CloudFront | us-east-1. |
| API Gateway Regional custom domain | Same Region as the API. |
| API Gateway edge-optimized custom domain | us-east-1. |
Exam cues
- If the question says public browsers and internal clients need different trust, think public ACM certificates and private CA certificates, because private trust must be installed in client trust stores.
- If the question says renew without repeated email approval, think DNS validation, because public CNAME records provide reusable domain-control proof.
- If the question says a certificate is unavailable to an endpoint, think its Region, because ALB and Regional APIs need local certificates while CloudFront and edge-optimized API domains use
us-east-1.
Remember
*.example.comcovers one subdomain level. It does not coverexample.comora.b.example.com.- The wildcard and base name share a DNS validation record; the token works across Regions.
- Public certificate domain validationDomain validation proves that a certificate requester controls each requested domain name. does not apply to imported or private CA certificates.
Trap: Sharing a DNS validation record does not extend a wildcard’s name coverage. Request the base domainA base domain is the domain name without a subdomain prefix. separately when it also needs coverage.
Trap: A private certificate is not publicly trusted merely because ACM manages it. Clients must trust the private root CA.
Publish the ACM-provided CNAME in the public DNS zone.
ACM establishes domain control before issuing the certificate.
Attach the certificate to an ALB in the same Region.
From the AWS docs (28)
- A certificate binds an identity to a public key.
- TLS protects client-server communication using authentication and encryption.
- A certificate authority issues signed certificates binding identities to public keys.
- ACM public certificates are trusted by major browsers and operating systems.
- Private certificates are not publicly trusted.
- ACM can issue private certificates through AWS Private CA integration.
- Private certificate trust is established by installing the appropriate root CA certificate in client trust stores.
- Imported certificates are customer certificates obtained outside ACM.
- ACM must establish control of every domain in a public certificate request.
- ACM domain ownership validation does not apply to imported certificates or private CA certificates.
- ACM cannot use private hosted zones or private domains for public certificate domain validation.
- DNS validation proves domain control using ACM-provided CNAME records added to the public DNS database.
- An existing DNS validation token can support certificate requests for the same domain across AWS Regions.
- A wildcard domain and its base domain receive the same DNS validation record.
- Email validation requires the domain owner to approve a validation email.
- HTTP validation uses a redirect from a domain URL to an ACM-controlled token location for CloudFront.
- A wildcard in the leftmost domain label covers one subdomain level, not the base domain or deeper subdomains.
- ACM integrates with Elastic Load Balancing to deploy a certificate to a load balancer.
- An ELB certificate must be in the same Region as its load balancer.
- CloudFront requires an ACM certificate requested or imported in US East (N. Virginia), us-east-1.
- An edge-optimized API Gateway custom domain requires a certificate in us-east-1.
- A Regional API Gateway custom domain requires an ACM certificate in the API Region.
- ACM certificates are Regional resources.
- DNS-validated ACM certificates in use can renew automatically while the validation CNAME records remain in place.
- AWS announced in August 2026 that email validation will be phased out during 2027.
- ACM does not renew imported certificates; the owner must get a new certificate from the issuer and reimport it before expiry, which keeps the same ARN.
- ACM publishes a DaysToExpiry CloudWatch metric twice a day for every certificate until it expires.
- The AWS Config managed rule acm-certificate-expiration-check flags certificates that expire within a set number of days, 14 by default.
Renewal, imports, and exports
ACM managed renewalManaged renewal is the ACM process for replacing eligible certificates before they expire. replaces eligible certificates before expiration. Renewal and installation are separate steps: integrated services can receive replacements automatically, while exported certificates need deployment to their target hosts.
How it works
- Check renewal eligibility. An ACM-issued certificateA certificate binds an identity to a public key using a digital signature. qualifies when associated with an integrated serviceAn integrated service can use an ACM certificate directly for its endpoint. or exported since issuance or its last renewal. Private certificates must be requested through ACM for this lifecycle.
- Preserve domain-control proof for public renewal. For a certificate used by an AWS service, the required DNSDNS is the directory system that holds records for names in a domain. CNAMEA CNAME record points one DNS name to another and can carry ACM domain-control proof. records must remain publicly accessible. Email renewal requires owner approval while that method remains supported.
- Let ACM renew eligible certificates. The ARNAn ARN identifies an AWS resource such as an ACM certificate., the AWS resource identifier, stays the same; copies in different Regions renew independently.
- Replace an imported certificate by renewing it with its issuer and reimporting it into the existing ARN. Supply PEMPEM is a text encoding used to represent certificates, chains, and keys., a text encoding for certificate material, and an unencrypted private keyA private key is the secret half of an asymmetric key pair that must be kept secure.. The certificate must be within its validity period.
- For an exported certificate, export the renewed certificate and install it on the host.
ACM Certificate Availablecan signal that a replacement is ready.
| Certificate path | Renewal owner | Deployment |
|---|---|---|
| Eligible ACM-issued certificate | ACM. | Integrated services receive replacements automatically. |
| Exported ACM-issued certificate | ACM, while eligible. | Customer exports and installs the replacement. |
| Imported certificate | Customer and original issuer. | ReimportReimport replaces an imported certificate while retaining its existing ARN and service associations. to preserve ARN and service associations. |
Direct Private CA IssueCertificate |
Customer. | Customer installs the certificate. |
Exam cues
- If the question says an imported certificate is expiring, think renew with the issuer and reimport, because imports are outside ACM managed renewal.
- If the question says a renewed export still serves an old certificate, think export and install the replacement, because renewal alone does not update the host.
- If the question says direct Private CA issuance should renew through ACM, think requesting through ACM and then exporting or associating it, because direct
IssueCertificateis ineligible. - If the question says avoid changing certificate references, think managed renewal or reimport into the existing ARN, because both preserve that identifier.
Remember
- Imported, expired, and directly issued Private CA certificates are ineligible for ACM managed renewal.
ACM Certificate Approaching Expirationcovers active public, private, and imported certificates.
Trap: Imported certificates are not eligible for ACM managed renewal. Renew with the issuer and reimport the replacement.
Trap: An exportable certificate is not automatically deployed to an external server after renewal. Your deployment process must retrieve and install the replacement.
The renewal workflow emits an event.
The private renewal example invokes Lambda to export the replacement.
Install the renewed certificate and key on the target; export alone does not install it.
From the AWS docs (23)
- ACM provides managed renewal for eligible public and private certificates that it issues.
- An ACM-issued certificate associated with an integrated AWS service is eligible for managed renewal.
- An ACM-issued certificate exported since issuance or its last renewal is eligible for managed renewal.
- Private certificates requested through ACM require export or service association for managed renewal eligibility.
- Imported certificates are not eligible for ACM managed renewal.
- Private certificates issued directly with AWS Private CA IssueCertificate are not eligible for ACM managed renewal.
- Expired certificates are not eligible for managed renewal.
- ACM certificates are Regional resources and each Region copy renews independently.
- An ACM certificate retains its ARN after managed renewal.
- DNS renewal for a certificate used by an AWS service requires all required validation CNAME records to remain accessible in public DNS.
- Email-validated renewal requires domain owner action on the renewal email.
- Reimporting a renewed certificate preserves the existing ARN and AWS service associations.
- Certificate import requires PEM-encoded certificate materials and an unencrypted private key.
- A certificate must be within its validity period when imported.
- Exportable ACM public certificates can be deployed on EC2, containers, or on-premises hosts.
- Customers must manage deployment of exported public certificates, including renewed certificates.
- Renewed private certificates update integrated services automatically; outside them customers must export and install replacements.
- ACM Certificate Available events notify when a certificate becomes available after issuance, renewal, or import.
- ACM Certificate Approaching Expiration events cover active public, private, and imported certificates.
- A certificate chain lists issuing certificates in order so each certifies the certificate before it.
- Direct Private CA issuance requires the customer to issue replacements and install certificates.
- The AWS private certificate renewal example uses EventBridge and Lambda to export a renewed certificate, followed by installation on its target.
- By default ACM sends the Approaching Expiration event daily, starting 45 days before expiry for imported and private certificates and 30 days before for public ones.
Validation migration and certificate lifecycle
AWS CertificateA certificate binds an identity to a public key using a digital signature. Manager (ACM) supports different validation and certificate lifecycle choices. These choices determine how domain control is proved, whether a certificate can be exported, and who manages renewal.
How it works
- Choose domain validationDomain validation proves that a certificate requester controls each requested domain name.. HTTPHTTP is the web communication protocol used to retrieve the redirect-based validation proof. validation is available through CloudFront Distribution Tenants, but it does not support wildcards. DNSDNS is the directory system that holds records for names in a domain. validation proves control through ACM-provided CNAMEA CNAME record points one DNS name to another and can carry ACM domain-control proof. records in public DNS.
- For an existing email-validated public certificate, use
UpdateCertificateOptionsto switch to DNS without changing its Amazon Resource NameAn ARN identifies an AWS resource such as an ACM certificate. (ARN). Add the CNAME records within 72 hours. - To allow public certificate export, set
CertificateOptions.ExporttoENABLEDat creation. The setting cannot change later. An export contains the certificate, its chain and a private keyA private key is the secret half of an asymmetric key pair that must be kept secure. encrypted with a passphraseA passphrase protects the private key returned by an ACM certificate export.. Private certificate exports also contain an encrypted private key. Export option, public export, private export - For ACM with an ACMEACME is a protocol that automates certificate issuance and lifecycle management between clients and certificate authorities. client, the client generates and holds the private key and manages public certificate renewal. ACME-issued certificates cannot bind to AWS integrated services and do not use ACM managed renewalManaged renewal is the ACM process for replacing eligible certificates before they expire.. Issuance options, managed renewal
Exam cues
- If the question says a CloudFront tenant needs a wildcard certificateA wildcard certificate covers names at one subdomain level using an asterisk in the leftmost label., think DNS validation, because HTTP validation does not support wildcards.
- If the question says preserve an email-validated certificate’s ARN, think
UpdateCertificateOptions, because it switches the certificate to DNS validation in place. - If the question says export an older public certificate, check its creation date and export setting, because certificates created before June 17, 2025 cannot be exported and the setting is fixed at creation.
- If the question says an ACME client holds the key, think client-managed renewal, because ACME-issued certificates do not use ACM managed renewal or bind to integrated services.
Remember
- From February 18, 2026, newly issued and renewed ACM public certificates have a maximum validity of 198 days.
- Public certificates with 198-day validity renew 45 days before expiration. Older 395-day certificates renew 60 days before expiration and receive 198-day replacements.
- ACM attempts renewal of eligible private certificates 60 days before expiration.
- New email-validated issuance stops March 31, 2027; renewal stops September 30, 2027.
Trap: HTTP validation is available for CloudFront Distribution Tenants, but it cannot validate a wildcard certificate. Use DNS validation for that request.
From the AWS docs (17)
- HTTP validation is available through CloudFront Distribution Tenants.
- HTTP validation does not support wildcard certificates.
- DNS validation proves domain control using ACM-provided CNAME records added to the public DNS database.
- Since August 13, 2026, an existing ACM-issued public certificate can switch from email to DNS through UpdateCertificateOptions without changing its ARN.
- Email-to-DNS migration provides 72 hours to add ACM CNAME records.
- From February 18, 2026, newly issued and renewed ACM public certificates have a maximum validity of 198 days.
- ACM public certificates created before June 17, 2025 cannot be exported.
- Set CertificateOptions.Export to ENABLED to permit export; the export option cannot change after certificate creation.
- A public certificate export includes the certificate, chain, and passphrase-encrypted private key.
- ACM private certificate export includes the certificate, certificate chain, and encrypted private key for private PKI use.
- Public certificates with 198-day validity renew 45 days before expiration; older 395-day certificates renew 60 days before expiration and receive 198-day replacements.
- ACM attempts eligible private certificate renewal 60 days before expiration.
- AWS announced in August 2026 that new email-validated certificate issuance stops on March 31, 2027.
- AWS announced in August 2026 that renewal of email-validated certificates stops on September 30, 2027.
- ACME clients generate and hold their private key and manage public certificate renewal.
- ACME-issued certificates cannot be bound to AWS integrated services.
- ACME-issued certificates do not use ACM managed renewal.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 22 cards as a list
A team needs TLS for a public ALB and private certificates trusted only within its organization. Which ACM certificate types fit?
Use an ACM public certificate on the ALB and ACM with AWS Private CA for private certificates. Private clients must trust the issuing root CA. Public certificate requests require proof of domain control.
A team wants an ACM public certificate to renew without recurring email approval. Which validation method should it choose?
Choose DNS validation and retain the public CNAME records. DNS validation proves control through those records; email validation requires owner approval.
A team requests ACM certificates for example.com and *.example.com. Does the wildcard alone also cover example.com or a.b.example.com?
No. A wildcard covers one subdomain level only. Include the base name separately; the wildcard and base name share the ACM DNS validation record.
A team must attach ACM certificates to an ALB in eu-west-1 and a CloudFront distribution. Where should the certificates be requested?
In
eu-west-1for the ALB andus-east-1for CloudFront. ELB uses a certificate from its own Region; CloudFront requires US East (N. Virginia).A team hosts an API Gateway Regional custom domain in eu-west-1 but selected an ACM certificate in us-east-1. What should it change?
Use an ACM certificate in the API Region,
eu-west-1. Theus-east-1requirement applies to edge-optimized custom domains.Can an ACM public certificate use a private Route 53 hosted zone to prove domain control?
No. ACM public certificate validation cannot use a private hosted zone or private domain. Publish the DNS validation CNAME in public DNS.
Third-party certificates imported into ACM must trigger an alert 30 days before they expire. What fits with the least effort?
The AWS Config managed rule acm-certificate-expiration-check with daysToExpiration set to 30, sending noncompliance to SNS. ACM never renews imported certificates, so they need this watch. A CloudWatch alarm on DaysToExpiry also works.
An ACM certificate on an ALB did not renew. Which validation and issuance conditions should the team inspect?
Check whether all DNS CNAME records remain publicly accessible or whether email renewal still needs approval. Imported certificates and private certificates issued directly by Private CA
IssueCertificatedo not use ACM managed renewal.A third-party certificate imported into ACM is expiring on an ALB. How should the team replace it without changing its ARN or service associations?
Renew it with its issuer and reimport into the existing ACM certificate ARN. ACM does not renew imported certificates. Import PEM materials and an unencrypted private key.
A team calls AWS Private CA IssueCertificate directly and expects ACM to renew the result. What should it change for ACM managed renewal?
Request the private certificate through ACM and associate it with an integrated service or export it. Direct
IssueCertificatecertificates are not eligible for ACM managed renewal.A team exported an ACM public certificate to an on-premises server. ACM renewed it, but the server still serves the old certificate. What is missing?
Export and deploy the renewed certificate on the server. ACM manages renewal, but the customer manages deployment of exported public certificates.
What happens to an ACM certificate ARN after managed renewal, and how are copies in multiple Regions handled?
The ARN stays the same. Each Regional certificate renews independently.
A team needs an EventBridge signal when an ACM certificate is renewed and ready for deployment. Which event should it match?
ACM Certificate Available. ACM also sendsACM Certificate Approaching Expirationfor active public, private, and imported certificates.Admins must get an email well before any ACM certificate on their load balancers expires, with the least custom code. What should they build?
An EventBridge rule matching ACM Certificate Approaching Expiration events, which ACM sends daily from 30 or 45 days before expiry, with an SNS topic as the target.
A CloudFront distribution tenant needs an ACM wildcard certificate. Can HTTP validation issue it?
No. HTTP validation is available through CloudFront Distribution Tenants but does not support wildcards. Use DNS validation for a wildcard certificate.
An existing email-validated ACM certificate must move to DNS validation while preserving ALB references to its ARN. What operation fits?
Use
UpdateCertificateOptionsto switch to DNS validation, then add the CNAME records within72 hours. AWS introduced this in August 2026 without changing the ARN.What validity period applies to newly issued or renewed ACM public certificates from February 2026?
A maximum of
198 days, effective February 18, 2026.A team wants to export an ACM public certificate created before June 17, 2025. Can it export the existing certificate?
No. Public certificates created before that date cannot be exported. Request an exportable replacement with
Export: ENABLED; that option cannot change after creation.What does an ACM public certificate export contain, and how is its private key protected?
The certificate, certificate chain, and private key encrypted with a supplied passphrase. ACM private certificate exports also contain an encrypted private key.
How do ACM renewal windows differ for current public certificates, older public certificates, and eligible private certificates?
Public certificates with
198-dayvalidity renew45 daysbefore expiry. Older395-daypublic certificates renew60 daysbefore expiry into198-dayreplacements. Eligible private certificates begin renewal attempts60 daysbefore expiry.A team still uses email validation for ACM public certificates. Which announced 2027 deadlines affect issuance and renewal?
New email-validated issuance stops March 31, 2027; renewal of email-validated certificates stops September 30, 2027. Migrate existing certificates to DNS before renewal support ends.
A team uses ACM with an ACME client on its own infrastructure. Who holds the private key and renews the certificate, and can it attach that certificate to an ALB?
The ACME client holds the private key and manages renewal. ACME-issued certificates cannot bind to AWS integrated services such as an ALB.