AWS Builder Center

Route 53 + CloudFront: how AWS gets users to your app, and gets your app to users fast

Route 53

Today I studied two services that work together at the “front door” of an application.
Route 53 is AWS’s DNS service. The name comes from port 53, the port DNS uses. It turns names like api.myshop.com into the IP addresses or AWS resources behind them. It also goes beyond basic DNS. It can run health checks, and it supports routing policies such as latency-based, weighted and failover. So it can send users to the healthiest or closest endpoint.
CloudFront is AWS’s CDN (content delivery network). It caches content at edge locations around the world. Requests are then served from a nearby edge instead of traveling all the way to your origin.
Why this matters: the farther away your server is, the higher the latency. Every request that reaches the origin also adds load.
For example, say you had an ASP.NET Core API behind a load balancer in us-east-1, backed by SQL Server on RDS, plus a React frontend stored in S3. Route 53 could point myshop.com and api.myshop.com to those resources. A failover record could send traffic to a static “maintenance” page if the API goes down. CloudFront could cache the frontend, and even GET endpoints like a product catalog. A user in Córdoba would get faster responses, and fewer of the same queries would hit SQL Server.
Question for you: what do you cache at the CDN level, and how do you handle invalidation when the data changes?
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article