Routing policies (simple, weighted, latency) in AWS - Mini Project: Build & Apply

Routing policies (simple, weighted, latency)

📖 Scenario: You are managing a website that needs to direct visitors to different servers based on simple, weighted, and latency routing policies. This helps improve user experience by controlling traffic flow and reducing delays.

🎯 Goal: Build a Route 53 hosted zone with three DNS records demonstrating simple, weighted, and latency routing policies.

📋 What You'll Learn

Create a hosted zone named example.com

Add a simple routing record for www.example.com pointing to 192.0.2.1

Add a weighted routing record for app.example.com with two IP addresses and weights

Add a latency routing record for api.example.com with two regions

💡 Why This Matters

🌍 Real World

Routing policies help direct internet traffic efficiently to improve website speed and availability.

💼 Career

Understanding DNS routing policies is essential for cloud engineers and network administrators managing scalable web applications.

1

Create the hosted zone

Create a Route 53 hosted zone named example.com using the AWS CLI command aws route53 create-hosted-zone with the name example.com.

AWS

# Use AWS CLI to create hosted zone example.com
# Your code here

Need a hint?

Use the aws route53 create-hosted-zone command with the --name option set to example.com.

2

Add a simple routing record

Add a simple routing record for www.example.com pointing to IP address 192.0.2.1 in the hosted zone example.com. Use the AWS CLI command aws route53 change-resource-record-sets with a JSON file named simple-record.json containing the record details.

AWS

aws route53 create-hosted-zone --name example.com --caller-reference 20240601-01
# Create simple-record.json with the simple routing record
# Your code here

Need a hint?

Create a JSON file with the record set for www.example.com using simple routing and then apply it with aws route53 change-resource-record-sets.

3

Add a weighted routing record

Add a weighted routing record for app.example.com with two IP addresses: 192.0.2.10 with weight 70 and 192.0.2.20 with weight 30. Use a JSON file named weighted-record.json and the AWS CLI command aws route53 change-resource-record-sets.

AWS

aws route53 create-hosted-zone --name example.com --caller-reference 20240601-01
# Add weighted routing records for app.example.com in weighted-record.json
# Your code here

Need a hint?

Use SetIdentifier and Weight fields in the JSON to create weighted routing records.

4

Add a latency routing record

Add a latency routing record for api.example.com with two records: one in us-east-1 region pointing to 192.0.2.100 and one in eu-west-1 region pointing to 192.0.2.200. Use a JSON file named latency-record.json and the AWS CLI command aws route53 change-resource-record-sets.

AWS

aws route53 create-hosted-zone --name example.com --caller-reference 20240601-01
# Add latency routing records for api.example.com in latency-record.json
# Your code here

Need a hint?

Use the Region and SetIdentifier fields in the JSON to create latency routing records.