Route 53 Health Checks Flashcards
What are Route 53 health checks?
Route 53 health checks monitor the health and performance of your web applications, web servers, and other resources. They can automatically reroute traffic when a resource becomes unhealthy.
How do Route 53 health checks work?
Health checks send automated requests to your application, server, or other resources at specified intervals. If a resource fails to respond correctly within a certain timeframe or exceeds failure thresholds, it is marked as unhealthy.
What types of health checks does Route 53 support?
Route 53 supports three main types of health checks: HTTP, HTTPS (both check the response from a web server at a given URL), and TCP health checks (check the response from a specified port).
Can Route 53 health checks monitor the status of resources not hosted in AWS?
Yes, Route 53 health checks can monitor the health of resources hosted both inside and outside AWS. This makes Route 53 a flexible option for monitoring a wide variety of web applications and services.
What is the difference between active and passive health checks in Route 53?
Active health checks actively send requests to resources to gauge their health, while passive health checks use Route 53 DNS request data to identify unhealthy resources without sending requests directly.
How can health checks integrate with Route 53 DNS routing?
Health checks can be linked to DNS records in Route 53. If a health check fails, Route 53 can automatically reroute traffic from the unhealthy resource to a healthy one based on DNS failover configurations.
What are health checkers in the context of Route 53?
Health checkers are the entities that Route 53 uses to perform health checks from various locations around the world. This helps ensure a comprehensive health assessment that factors in global accessibility.
How do you configure notifications for health check failures in Route 53?
Notifications for health check failures can be configured through Amazon CloudWatch alarms. When a health check fails, CloudWatch alarms can trigger notifications via Amazon SNS to alert administrators.
What role does string matching play in Route 53 health checks?
String matching allows you to specify a string that Route 53 looks for in the response body of an HTTP/HTTPS health check. If the specified string is not found, the health check is considered failed.
How does Route 53 handle health checks for endpoints with dynamic IP addresses?
Route 53 health checks can be configured to resolve the domain name of the endpoint afresh with each check, accommodating endpoints with dynamic IP addresses by always using the most current IP for health assessments.
