When you host a website or run a web application on Elastic Compute Cloud instances, it's important to give your...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
instances intuitive names -- so you don't force end users to remember a string of IP addresses. The Amazon Route 53 service can help facilitate this process.
Amazon Route 53 provides a scalable and highly available domain name system that connects end-user requests for sites into IP addresses; other AWS tools then can read and deliver necessary content. For example, an end-user request to a Route 53 domain would ping an Elastic Compute Cloud (EC2) instance and an Amazon Simple Storage Service bucket.
Following are step-by-step instructions explaining how to register a Route 53 domain name and then route traffic for the domain to the server that hosts your website or web application.
After registering the domain, follow these steps to route it to EC2:
1. Get the IP address of the EC2 instance, sign in and open the EC2 console. Choose the region and EC2 instances you want and then choose the instance to which you want to route traffic. On the Description tab, get the value of the Public IP.
2. Open the Amazon Route 53 console.
3. Select Hosted Zones in the navigation pane.
4. Select the hosted zone name for the Route 53 domain name to route traffic to EC2.
5. Choose Create Record Set.
6. Specify the following:
- Name -- Enter the name of the hosted zone. If it is example.com and you want to use my.example.com to route traffic to EC2, then only type my.
- Type -- Choose an IPV4 address.
- Alias -- Choose No.
- TTL -- Stay with the default 300 seconds.
- Value -- Type the IP address from Step 1.
- For Routing Policy, choose Simple.
7. Click Create.
Control AWS traffic with Amazon Route 53
Weigh the pros and cons of Route 53
Don't fall into the single cloud provider trap
Dig Deeper on Amazon EC2 (Elastic Compute Cloud) management
Related Q&A from Ofir Nachmani
Security should be a top priority in public cloud deployment, but breaches are still possible. If your AWS account has been hacked, follow these ...continue reading
AWS users in the US-East-1 region have seen a string of outages in the last few years. But does that mean they shouldn't deploy workloads there?continue reading
Reserved Instances save IT teams money on compute resources but lock them into a particular type of instance. How do Convertible RIs differ, and what...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.