- Newest
- Most votes
- Most comments
I think CloudFront would be a good fit for this - it will provide the lowest latency for your users as the redirect will be served from their nearest Point of Presence (POP), and the volume of traffic should be low enough to fit into the free tier.
There are a number of ways you could set this up, but I think the simplest would be to put an index.html into an S3 bucket, and serve that through CloudFront. This is outlined in detail here. Your index.html should simply redirect the user to the target URL. If it is unlikely to change, then you can set long TTL values in CloudFront to maximize the number of requests that will be served from cache.
Note that Origin Access Identities specified in the article linked above have been superseded by Origin Access Control .
Relevant content
- asked 4 years ago
- asked a year ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago
Thanks! Followed the instructions up to where it says I need to point a CNAME record at the CloudFront distribution. That sounds like I need to create a CNAME record at the domain apex, which is impossible? Could you clarify please?
Route53 has a special resource type called an Alias which can be used for the domain apex: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-cloudfront-distribution.html