AwsCLI icon
If icon
SlackIncomingWebhook icon
Schedule icon

AWS Route53 DNS Health Check Failure and Failover Sentinel

Audits AWS Route53 health checks to detect endpoint outages and verify automated DNS failover behavior.

Categories
CloudInfrastructure

How it works

This sentinel leverages AwsCLI to query aws route53 get-health-check-status for the specified health check identifier. It evaluates status reports across all global checker observation points, alerting SRE teams when a majority of observers report HTTP failure or connection timeouts.

What you get

  • Real-time detection of external endpoint outages before end users report downtime.
  • Automated verification that Route53 DNS failover routing policies engage correctly.
  • Automated Slack delivery tracking failed observation counts, checker regions, and error descriptions.

Who it's for

  • Site reliability engineers (SREs) and network administrators maintaining public DNS routing.
  • DevOps teams supervising multi-region disaster recovery endpoints.

Why orchestrate this with Kestra

Kestra runs automated scheduled operational health checks with native error handling, secret injection, and multi-channel alerting.

Prerequisites

  • AWS IAM credentials with route53:GetHealthCheckStatus permissions.
  • Secrets AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and SLACK_WEBHOOK configured in Kestra.

Quick start

  1. Import this blueprint into Kestra.
  2. Configure health_check_id and credentials.
  3. Run manually to check current health check observations.

How to extend

  • Query CloudWatch metrics for HealthCheckPercentageHealthy concurrently.
  • Automatically trigger synthetic canary runs to verify SSL certificate or application response validity.
  • Forward DNS failover events to PagerDuty or an incident war room.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.