AWS Route 53 and Routing Policies

Figure 01 — Simple Routing Policy
Figure 02 — Simple Routing Policy Entry
Figure 03 — Fail-over Routing Policy
Figure 04 — Crating a “health check”

Name: test.mydomain.com

Type: A Record

Alias: No

Value: <Public-IP> of EC2 instance

Routing Policy: Fail-over

Fail-over Record Type: Primary (Do not change SetID)

Associate with Health Check: Select “Yes” and select the created Health Check record

Figure 05 — The “Non Alias” primary “A” record with a “Fail-over” routing policy

Name: test.mydomain.com

Type: A Record

Alias: Yes

Value: <S3 bucket public URL>

Routing Policy: Fail-over

Fail-over Record Type: Secondary (Do not change SetID)

Associate with Health Check: Select “No”

Figure 06 — The “Alias” secondary “A” record with a routing policy
Figure 07 — Blue Green Deployment [1]

Blue Green Deployment: You can use this approach while bringing a software product from the final stage of testing to live production. This is also known as the “cut over”. With this approach, it ensures you have two production environments as identical as possible. At any given point you can switch the traffic to one of the endpoints depending on your requirement.

Figure 08 — Weighted Routing Policy

Type: A Record

Alias: No

Value: <The public URL of the EC2 instance>

Routing Policy: Weighted (Weight = 90, Set Id = ec2)

Figure 09 — EC2 endpoint with 90% weight

Type: A Record

Alias: Yes

Value: <The public URL of the S3 bucket>

Routing Policy: Weighted (Weight = 10, Set Id = s3)

Figure 10 — S3 Web hosting with 1endpoint 10% weight
Figure 11 — Latency based Routing Policy

Type: “A” Record
Alias: No
Value: <The public URL of the EC2 instance>
Routing Policy: Latency
Region: <us-east-1>
SetID: <Any-identifier>
Health Check: <if-required>

Figure 12 — EC2 instance in us-east-1

Type: “A” Record
Alias: No
Value: <The public URL of the EC2 instance>
Routing Policy: Latency
Region: <ap-southasia-1>
SetID: <Any-identifier>
Health Check: <if-required>

Figure 13 — EC2 instance in ap-southeast-1
Figure 14 — Geo Location Policy for Locations Washington (USA) and Sri Lanka

Type: A Record

Alias: No

Value: <The public URL of the EC2 instance>

Routing Policy: Geo-Location

Location: Select a location closer to the EC2 instance region us-east-1 (Washington)

SetID: <Any-identifier>

Health Check: <if-required>

Figure 15 — Geo Location “A” record for the location “Washington”

Alias: No

Value: <The public URL of the EC2 instance>

Routing Policy: Geo-Location

Location: Select a location closer to the EC2 instance region ap-southasia-1 (Sri Lanka)

SetID: <Any-identifier>

Health Check: <if-required>.

Figure 16: Geo Location “A” record for the location “Sri Lanka”
Figure 17 — Multi-value routing policy
Figure 18
Figure 19
Figure 20 — Multi-value routing policy

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store