You cannot use R53 health checks as canaries

[seth_e]

you say

> The option that says: Change the target group health check to a simple HTML page instead of a page that queries the database. Create an Amazon Route 53 health check for the database dummy item web page to ensure that the application works as expected. Set up an Amazon CloudWatch alarm to send a notification to Admins when the health check fails is correct. Changing the target group health check to a simple HTML page will reduce the queries to the database tier. The Route 53 health check can act as the “external” check on a specific page that queries the database to ensure that the application is working as expected. The Route 53 health check has an overall lower request count compared to using the target group health check.

No. Route 53 is not even used in this example. And Route 53 health checks are used by Route 53 for routing decisions. What you want users to create here is a CloudWatch canary using synthetic monitoring

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries.html

[Kenneth-Samonte-Tutorials-Dojo]

Hi seth_e,

Thank you for your feedback.

This question focuses on the topic of Route 53 health check in the ElastiCache cluster.

I understand that on AWS, there are many ways to implement a solution with the desired outcome.

Some solutions are more optimal or effective than others. While others solutions are faster to implement without much changes to the existing infrastructure.

Each solution depends on which approach you want to take on depending on the scenario.

Hope this helps.

Let us know if you need further assistance. The Tutorials Dojo team is dedicated to helping you pass your AWS exam!

Regards,

Kenneth Samonte @ Tutorials Dojo