Topic lessonTopic: Route 53 and ACM: names and HTTPS
AWS Certificate Manager explained: CloudFront TLS, validation and renewal
ACM issues and manages TLS certificates. Creating a certificate and configuring it correctly where it is used are separate tasks. Follow a public report site through hostname coverage, Region selection, DNS validation and deployment after renewal.
Distinguish viewer/origin TLS, validation/traffic DNS records, and certificate renewal/deployment.
TLS authenticates connection endpoints and encrypts HTTPS traffic. A certificate’s SAN lists covered names. Do not disclose or enter private keys; this lesson issues no certificates and changes no DNS records.
Viewer and origin TLS are separate connections
- Viewer → CloudFrontConnection 1: viewer-to-CloudFront HTTPS
- CloudFront → ALB originConnection 2: origin HTTPS when a fetch is required
- Viewer
- Requests reports.example.com
- CloudFront
- Associate the viewer certificate
- ALB origin
- Origin TLS has separate requirements
| Use | Region | Check |
|---|---|---|
| Viewer → CloudFront | us-east-1 (US East, N. Virginia) | SAN covers the public reports.example.com name. |
| CloudFront → Tokyo ALB | Certificate in the ALB’s Region | Origin request hostname and certificate coverage. |
Match certificate names to the names actually used
Check that the requested hostname is covered by the Subject Alternative Name (SAN). A certificate wildcard *.example.com covers names at that level, such as reports.example.com. It does not alone cover example.com or a.reports.example.com.
| Requested name | Covered? | Reason |
|---|---|---|
| reports.example.com | Yes | At the wildcard’s level. |
| example.com | No | The apex needs its own coverage. |
| a.reports.example.com | No | One additional label below that level. |
Separate validation CNAMEs from traffic records
For DNS validation of a public ACM certificate, publish ACM’s specified CNAME name/value pair to prove domain control. DNS can be hosted outside Route 53. This validation record is separate from the record directing site visitors.
| Purpose | Example name | Role |
|---|---|---|
| Site traffic | reports.example.com | Point the name toward CloudFront with a supported record. |
| ACM DNS validation | Validation name supplied by ACM | Prove control using ACM’s required CNAME value. |
Manage renewal eligibility, validation and deployment separately
| Certificate path | Renewal check | Deployment check |
|---|---|---|
| ACM-issued, used by an integrated AWS service | Maintain managed-renewal eligibility and validation | Correct association and the certificate actually served. |
| Exportable public certificate | Check that the renewed certificate is available | Owner deploys the replacement securely to the server. |
| Externally issued certificate imported into ACM | Not eligible for ACM managed renewal | Manage external renewal and reimport/replacement. |
| ACME issuance | Renewal is handled by the ACME client, not ACM managed renewal | Verify client/deployment automation and failure detection. |
For C3’s DNS-validated certificate in use by an integrated service, check public accessibility of the required CNAMEs and renewal status. An Issued status alone is not a guarantee of future renewal. Expired and imported certificates have different eligibility.
Check usage and cost conditions as well as the certificate
Non-exportable public certificates for integrated services, exportable certificates, ACME and Private CA have different pricing conditions. Using ACM does not make the entire site free. Check CloudFront/ALB and other usage charges separately; this lesson assumes no fixed price or certificate lifetime.
- Identify names and services on viewer and origin connections.
- Check Region, SAN and required certificate-chain conditions.
- Verify validation and traffic DNS records separately.
- Identify issuance/import/export/ACME and renewal ownership.
- Verify the certificate actually served and the HTTP response after renewal.
- Define failure/expiry detection and the responsible response procedure.
Check the conditions from issuance to use
Choose an option to see the result and explanation.
Check, then explain in your own words
- Separate C3’s TLS connections and Regions.
- Check SAN and wildcard depth.
- Distinguish validation CNAMEs from traffic DNS.
- Explain renewal/deployment ownership per certificate path.
Check your understanding: What is not established by “the certificate has renewed”?
Correct deployment and the connection actually using the renewed certificate.
Managed renewal, validation, association and custom-server deployment are separate checks.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsViewer ACM certificate in us-east-1 versus the separate origin TLS connection. Documentation review, not live AWS verification.
Used in this lessonViewer and origin TLS are separate connections Check the conditions from issuance to use
- AWS Certificate Manager overviewChecked:
Scope and conditionsIssuance, import, service association and regional certificate resources. Documentation review, not live AWS verification.
Used in this lessonViewer and origin TLS are separate connections
Scope and conditionsDNS target, distribution alias and certificate SAN are separate checks; certificate wildcard scope. Documentation review, not live AWS verification.
Used in this lessonViewer and origin TLS are separate connections Match certificate names to the names actually used Check the conditions from issuance to use
- ACM: DNS validationChecked:
Scope and conditionsPublic DNS validation CNAME versus a traffic record; retain validation records. Documentation review, not live AWS verification.
Used in this lessonSeparate validation CNAMEs from traffic records Check the conditions from issuance to use
Scope and conditionsAlias targets, apex, record type and TTL; not an HTTP redirect. Documentation review, not live AWS verification.
Used in this lessonSeparate validation CNAMEs from traffic records
Scope and conditionsIn-use and publicly resolvable required CNAME checks for DNS-validated integrated-service renewal. Documentation review, not live AWS verification.
Used in this lessonSeparate validation CNAMEs from traffic records Manage renewal eligibility, validation and deployment separately
- ACM: Managed certificate renewalChecked:
Scope and conditionsRenewal eligibility depends on issuance and usage/export; imported certificates are not managed-renewal eligible. Documentation review, not live AWS verification.
Used in this lessonManage renewal eligibility, validation and deployment separately Check the conditions from issuance to use
Scope and conditionsExportable public certificates, private-key protection and owner-managed deployment of renewals. Documentation review, not live AWS verification.
Used in this lessonManage renewal eligibility, validation and deployment separately Check the conditions from issuance to use
- AWS Certificate Manager pricingChecked:
Scope and conditionsDistinguish non-exportable public and exportable certificate pricing; no fixed-price guarantee. Documentation review, not live AWS verification.
Used in this lessonCheck usage and cost conditions as well as the certificate