Exploring Route 53 Routing Policies - 3
- Hafeez Baig |
- 24 steps |
- 2 minutes
Refer to the following guide to learn how to use IAM in the cloud\ <https://scribehow.com/shared/Creating_an_IAM_User_and_User_Group_in_AWS_Management_Console__hWNiiXlcRJKFqYZZEJD-cg> Refer to this guide to learn how to create Route 53 and EC2 Instances\ <https://scribehow.com/shared/Creating_a_Hosted_Zone_with_Route_53_and_Exploring_Routing_Policies__FArAHxUbTHm8x2OZckeTrw>
Sign in to **AWS Management Console** as an **IAM User** **Pre-requisite** - Ensure you have selected the AWS region closest to your location\ For this guide, we will be using us-east-2 (Ohio) as a preferred choice
Type **Route 53** in the search bar and click on **Route 53** to view the Route 53 Dashboard
**What is Route 53?** Route 53 is an AWS DNS web service that manages domain names and directs internet traffic to resources based on rules and configurations set by the user.
On **Route 53** dashboard, click on the **Hosted zones** from the left bar
**Hosted zones** wizard will open, select the Hosted zone name **learnaws.com**
**What are Hosted zones?** Hosted zones are containers within a DNS service that store records mapping domain names to IP addresses or other resources, enabling control over DNS resolution for a domain.
Click on the **View details** button on the top right side
**learnaws.com** wizard will open, click on the **Create record** button on the right side
**Create record wizard** will open, scroll to the **Routing policy** section and from the dropdown select the option **Failover**
**What is the Failover Routing policy?** The Failover routing policy in DNS automatically redirects traffic from a primary resource to a secondary resource if the primary becomes unavailable, ensuring high availability.
Scroll to the Failover record type secton and from the dropdown select the option **Primary**
**What are Primary and Secondary failover types?** - **Primary Failover**: This type involves designating one resource (e.g., server, database, or service) as the primary resource that handles incoming traffic or requests under normal operating conditions. If this primary resource fails or becomes unavailable, failover mechanisms are triggered to redirect traffic to alternative resources. - **Secondary Failover**: In contrast, the secondary failover involves designating another resource as a backup or a secondary resource that remains inactive under normal conditions but becomes active if the primary resource fails. The secondary resource serves as a standby, ready to take over operations in case of primary resource failure.
To create a new record for **Geolocation** policy, give the **Record name** as "**geolocation**" in text input field
Open the text editor and copy the **Mumbai** instance IP address
Scroll to the **Value** section and paste the copied IP address of the Mumbai instance in the text input field
Scroll to the **TTL(seconds)** section and enter "**10**" in the text input field
**What is TTL(seconds)?** TTL (Time To Live) is a parameter in DNS records that specifies how long the record can be cached by DNS resolvers, measured in seconds.
Scroll to the **Routing policy** section and from the dropdown select the option **Geolocation**
**What is Geolocation Routing policy?** Geolocation routing policy in DNS directs traffic to different endpoints based on the geographic location of the client, optimizing performance and providing a customized experience.