routing-traffic-with-route53-and-cloudfront

Configures Route 53 alias records to route custom domain traffic to CloudFront distributions.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill routing-traffic-with-route53-and-cloudfront-sakicodes
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/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/routing-traffic-with-route53-and-cloudfront
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill routing-traffic-with-route53-and-cloudfront-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up a custom domain for a CloudFront distribution involves coordinating DNS records, ACM certificates, and distribution settings across multiple AWS services, which is error-prone when done manually. ## Core Features & Use Cases - Alias Record Creation: Creates A and AAAA alias records in Route 53 pointing to a CloudFront distribution, including IPv6 support. - ACM Certificate Setup: Requests and validates SSL certificates in us-east-1 and attaches them to the CloudFront distribution for HTTPS. - Hosted Zone Management: Finds or creates public hosted zones and monitors DNS propagation. - Use Case: You have a CloudFront distribution serving your website and want www.example.com to serve traffic over HTTPS. This Skill walks through certificate validation, CNAME configuration, and DNS record creation end to end. ## Quick Start Ask the assistant to route traffic for your custom domain to your CloudFront distribution by providing the domain name and distribution ID.

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 point a custom domain to a CloudFront distribution with Route 53?

Create an alias A record in a public Route 53 hosted zone pointing to the CloudFront distribution domain name, using the CloudFront hosted zone ID Z2FDTNDATAQYW2. The domain must first be added as an alternate domain name (CNAME) on the distribution.

How to set up HTTPS for CloudFront with an ACM certificate?

Request an ACM certificate with DNS validation in the us-east-1 region, which is required for CloudFront. Create the validation records in Route 53, wait for validation, then update the distribution to use the certificate ARN with SNI support.

Does CloudFront work with private Route 53 hosted zones?

No, CloudFront distributions only work with public hosted zones. If only a private hosted zone exists for the domain, you must create a public hosted zone or transfer DNS management to Route 53 for public resolution.

Why is my Route 53 alias record for CloudFront not working?

The most common cause is that the domain is not listed as an alternate domain name (CNAME) in the CloudFront distribution configuration. Add the domain to the distribution first, then verify the record uses the correct CloudFront hosted zone ID.

How long does DNS propagation take for Route 53 changes?

Route 53 changes typically propagate within 60 seconds, but full global propagation can take up to 48 hours. Verify resolution with nslookup or dig and test from multiple locations.