routing-traffic-with-route53-and-cloudfront

Configure Route 53 alias records and ACM certificates for CloudFront HTTPS routing.

2.3k|234|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill routing-traffic-with-route53-and-cloudfront-aws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: routing-traffic-with-route53-and-cloudfront
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/networking-and-content-delivery-skills/routing-traffic-with-route53-and-cloudfront
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill routing-traffic-with-route53-and-cloudfront-aws

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configures Route 53 to route traffic to a CloudFront distribution using a custom domain, handling DNS alias records, alternate domain names, and HTTPS via ACM.

Core Features & Use Cases

  • Alias DNS setup: Create public Route 53 alias A and AAAA records that point to CloudFront distributions.
  • SSL/TLS enablement: Associate ACM certificates with CloudFront for HTTPS on custom domains.
  • IPv6 support: Enable IPv6 for CloudFront distributions to reach modern clients.
  • Use Case: Route example.com to a CloudFront distribution with TLS, with Route 53 managing DNS and domain validation.

Quick Start

Provide the domain name, distribution ID, hosted zone details, and region to begin configuring Route 53 routing to CloudFront.

Frequently Asked Questions about routing-traffic-with-route53-and-cloudfront

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route Route 53 DNS to a CloudFront distribution with a custom domain?

Route 53 routing to CloudFront requires providing your domain name, distribution ID, hosted zone details, and region. You need an active CloudFront distribution and a public Route 53 hosted zone to begin configuration.

How do I enable HTTPS on a CloudFront custom domain using ACM?

Enable HTTPS on CloudFront by provisioning an ACM certificate and associating it with your distribution as an alternate domain name. The certificate must be requested in the correct region and validated before CloudFront accepts it.

Do I need to create both A and AAAA alias records for CloudFront in Route 53?

Creating both alias A and AAAA records in Route 53 is required when IPv6 support is enabled on your CloudFront distribution. This ensures traffic reaches clients using both IPv4 and IPv6 protocols.

What is the best way to configure DNS alias records for CloudFront?

The best way to configure DNS alias records for CloudFront is using Route 53 alias A and AAAA records. This approach maps your apex or subdomain to the distribution endpoint without standard CNAME restrictions.

Why is my Route 53 alias record not resolving to my CloudFront distribution?

Route 53 alias records fail to resolve to CloudFront when the alternate domain name CNAME is missing from the distribution configuration. Ensure the custom domain matches the ACM certificate and the hosted zone is correctly selected.