Back to Details

routing-traffic-with-route53-and-cloudfront

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Routing Traffic with Route 53 and CloudFront

使用Route 53和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.
本内容专注于使用自定义域名配置Amazon Route 53将流量路由到Amazon CloudFront分发的领域知识，涵盖托管区域管理、别名A/AAAA记录、备用域名（CNAME）配置以及用于HTTPS的ACM证书设置。

Configure Route 53 to route traffic to a CloudFront distribution

配置Route 53以将流量路由到CloudFront分发

To set up a custom domain for a CloudFront distribution with Route 53 DNS, follow the procedure exactly. See Route 53 CloudFront routing procedure.
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
要通过Route 53 DNS为CloudFront分发设置自定义域名，请严格遵循以下步骤。 查看Route 53 CloudFront路由步骤。
该步骤涵盖：
  • 验证CloudFront分发状态和CNAME配置
  • 申请并验证ACM证书（必须位于us-east-1区域）
  • 创建或查找公共托管区域
  • 创建指向CloudFront的别名A和AAAA记录
  • 监控DNS传播

Troubleshooting

故障排查

Domain not in CloudFront CNAMEs

域名未在CloudFront CNAME中

Add the domain as an alternate domain name in the CloudFront distribution configuration before creating Route 53 records.
在创建Route 53记录之前，需在CloudFront分发配置中将该域名添加为备用域名。

SSL certificate issues

SSL证书问题

ACM certificates for CloudFront must be in us-east-1. Ensure the certificate is validated and associated with the distribution.
用于CloudFront的ACM证书必须位于us-east-1区域。确保证书已验证并与分发关联。

Private hosted zone

私有托管区域

CloudFront only works with public hosted zones. Create a public hosted zone if only a private one exists.
CloudFront仅适用于公共托管区域。如果仅存在私有托管区域，请创建一个公共托管区域。

DNS propagation delays

DNS传播延迟

Changes typically propagate within 60 seconds but full global propagation can take up to 48 hours. Use 
nslookup
or 
dig
to verify.
更改通常会在60秒内完成传播，但全球完全传播可能需要长达48小时。使用
nslookup
或
dig
工具进行验证。