# routing-traffic-with-route53-and-cloudfront

Points a custom domain at a CloudFront distribution in Route 53, with alias records, alternate domain names, ACM certificates and IPv6.

Skill by Amazon Web Services. Category: Shipping and ops.

## Install

Project (for this project only):

```sh
npx skills add aws/agent-toolkit-for-aws --skill routing-traffic-with-route53-and-cloudfront
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add aws/agent-toolkit-for-aws --skill routing-traffic-with-route53-and-cloudfront -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 5679. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/aws/agent-toolkit-for-aws/routing-traffic-with-route53-and-cloudfront)

## Source

[Open the source](https://github.com/aws/agent-toolkit-for-aws/tree/HEAD/skills/specialized-skills/networking-and-content-delivery-skills/routing-traffic-with-route53-and-cloudfront). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: routing-traffic-with-route53-and-cloudfront
description: Configures Amazon Route 53 to route traffic to a CloudFront distribution using a custom domain. Use when setting up DNS alias records, alternate domain names (CNAMEs), ACM certificates for HTTPS, and IPv6 support for CloudFront.
version: 1
---

# Routing Traffic with Route 53 and CloudFront

## Overview

Domain expertise for configuring Amazon Route 53 to route traffic to Amazon CloudFront distributions using custom domain names. Covers hosted zone management, alias A/AAAA records, alternate domain name (CNAME) configuration, and ACM certificate setup for HTTPS.

## Configure Route 53 to route traffic to a CloudFront distribution

To set up a custom domain for a CloudFront distribution with Route 53 DNS, follow the procedure exactly.
See [Route 53 CloudFront routing procedure](references/route53-cloudfront-routing.md).

The procedure covers:

- Verifying CloudFront distribution status and CNAME configuration
- Requesting and validating ACM certificates (must be in us-east-1)
- Creating or locating public hosted zones
- Creating alias A and AAAA records pointing to CloudFront
- Monitoring DNS propagation

## Troubleshooting

### Domain not in CloudFront CNAMEs

Add the domain as an alternate domain name in the CloudFront distribution configuration before creating Route 53 records.

### SSL certificate issues

ACM certificates for CloudFront must be in us-east-1. Ensure the certificate is validated and associated with the distribution.

### Private hosted zone

CloudFront only works with public hosted zones. Create a public hosted zone if only a private one exists.

### DNS propagation delays

Changes typically propagate within 60 seconds but full global propagation can take up to 48 hours. Use `nslookup` or `dig` to verify.
````

- Previous: [creating-api-gateway-stage](https://syn4pse.dev/terminal/creating-api-gateway-stage.md)
- Next: [setting-up-ec2-instance-profiles](https://syn4pse.dev/terminal/setting-up-ec2-instance-profiles.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
