Route 53 Evaluate Target Health

Overview

Configuration

The idea is to create failover record, primary record points to internal ALB, secondary record points to S3 website endpoint, select evaluate target health for both records.

ALB Target Health

When we hard code the response code from ALB to 200, the primary resource is considered as healthy, so DNS query returns my internal ALB IP address.

>nslookup blog.rquan.<xyz>Non-authoritative answer:
Name: blog.rquan.<xyz>
Addresses: 10.0.2.138
10.0.1.185
>nslookup blog.rquan.<xyz>Non-authoritative answer:
Name: blog.rquan.<xyz>
Address: 52.217.111.131

S3 Website Endpoint Target Health

I switch around failover records, S3 as the primary and ALB as secondary. I’m hoping to update S3 so that it becomes unhealthy and returns secondary record IP address.

  • Remove index html file
  • Disable S3 static web site
  • Delete bucket

Conclusion

Now we have better understanding of alias record and evaluate target health, let’s think about “Standby takes over primary” pattern (STOP).

References

Configuring a static website using a custom domain registered with Route 53 — Amazon Simple Storage Service

--

--

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
Cloud Journey

Cloud Journey

All blogs are strictly personal and do not reflect the views of my employer, focus on cloud networking, cloud security and API security.