Amazon Route 53, a highly available and scalable Domain Name System (DNS) service.
AWS also introduced the Route 53 health checks,inorder to configure the traffic between Primary and Secondary sites for higher availability and monitor the health and performance of the web applications, servers, and other resources.These are based on public IPv4 addresses.
AWS enhanced this feature and introduced the domain name health checks,which help the customers in a better way for managing the availability of the services.
Domain name based health checks with Cloud Watch alarms,can be used for creating a distributed monitoring system for Amazon AWS resources. Currently, Route 53 health checks support only resources that are publicly reachable. URL monitoring will be from a single instance and a fixed location. It is known to be a single point of failure and also difficult for achieving high availability in monitoring.
We can monitor all our EC2-Classic and VPC public subnet machines availability, services monitoring from the different geographical locations of Amazon AWS Network, with Route53 health checks. Also URL monitoring for all our applications.
In addition to these, we can even monitor our in-house or co-location applications availability.
Health checks can be created for HTTP/HTTPS/TCP based protocol services and choose the Request interval, failure threshold and create a cloud watch alarm to alert us in case of failure.
AWS published the list of current IP ranges used by Amazon Route 53 health checkers.
- You can open these range of IP Addresses in Security Groups for monitoring your services.
- It would be a good practice to create a new separate security group.
- Allow the IP Addresses and attach it to the instance while launching the instance.
Private IP addresses or private DNS health checks monitoring is still missing. Since AWS is forcing everyone to use VPC, which would support private resources monitoring that adds a great feature to the health checks.