INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Distinguish viewer/origin TLS, validation/traffic DNS records, and certificate renewal/deployment.

Prerequisite

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

C3: two HTTPS connections using CloudFront and an ALB in Tokyo
C3: two HTTPS connections using CloudFront and an ALB in Tokyo1: Viewer — Connection 1: viewer-to-CloudFront HTTPS — CloudFront. 2: CloudFront — Connection 2: origin HTTPS when a fetch is required — ALB origin12ViewerCloudFrontALB originC3: two HTTPS connections using CloudFront and an ALB in Tokyo1: Viewer — Connection 1: viewer-to-CloudFront HTTPS — CloudFront. 2: CloudFront — Connection 2: origin HTTPS when a fetch is required — ALB origin12ViewerCloudFrontALB origin
  1. Viewer → CloudFrontConnection 1: viewer-to-CloudFront HTTPS
  2. 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
ACM certificate placement in C3
UseRegionCheck
Viewer → CloudFrontus-east-1 (US East, N. Virginia)SAN covers the public reports.example.com name.
CloudFront → Tokyo ALBCertificate in the ALB’s RegionOrigin 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.

With only *.example.com in the SAN
Requested nameCovered?Reason
reports.example.comYesAt the wildcard’s level.
example.comNoThe apex needs its own coverage.
a.reports.example.comNoOne 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.

Two DNS purposes in C3
PurposeExample nameRole
Site trafficreports.example.comPoint the name toward CloudFront with a supported record.
ACM DNS validationValidation name supplied by ACMProve control using ACM’s required CNAME value.

Manage renewal eligibility, validation and deployment separately

Certificate paths carry different remaining responsibilities
Certificate pathRenewal checkDeployment check
ACM-issued, used by an integrated AWS serviceMaintain managed-renewal eligibility and validationCorrect association and the certificate actually served.
Exportable public certificateCheck that the renewed certificate is availableOwner deploys the replacement securely to the server.
Externally issued certificate imported into ACMNot eligible for ACM managed renewalManage external renewal and reimport/replacement.
ACME issuanceRenewal is handled by the ACME client, not ACM managed renewalVerify 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.

  1. Identify names and services on viewer and origin connections.
  2. Check Region, SAN and required certificate-chain conditions.
  3. Verify validation and traffic DNS records separately.
  4. Identify issuance/import/export/ACME and renewal ownership.
  5. Verify the certificate actually served and the HTTP response after renewal.
  6. 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.

Where is C3’s ACM certificate for viewer-to-CloudFront HTTPS provisioned?
Read the answer and reason

Answer: us-east-1 · CloudFront viewer ACM certificates require US East (N. Virginia).

With only *.example.com in the SAN, is example.com itself covered?
Read the answer and reason

Answer: No; the apex needs its own coverage · The wildcard’s level does not include the apex itself.

Does publishing the ACM validation CNAME also route site traffic to CloudFront?
Read the answer and reason

Answer: No; configure traffic DNS separately · The validation CNAME proves domain control.

Does importing an external certificate guarantee ACM managed renewal?
Read the answer and reason

Answer: No; imported certificates need separate renewal management · Imported certificates are not eligible for ACM managed renewal.

Does ACM renewal of an exported certificate complete deployment on a custom server?
Read the answer and reason

Answer: No; verify secure deployment and the served certificate · Manage retrieval/deployment and verify the version actually in use.

Check, then explain in your own words

  1. Separate C3’s TLS connections and Regions.
  2. Check SAN and wildcard depth.
  3. Distinguish validation CNAMEs from traffic DNS.
  4. 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.