Create Health Checks – Step 1: Configure health check
- Route53 > Health checks
- Configure health check
- Name
- What to monitor
- Endpoint
- Status of other health checks (calculated health check)
- State of Cloudwatch alarm
- Monitor an endpoint
- Specify by:
- IP
- Domain name
- Caution using this. It will prevent you from creating a failover record in Route 53 since both IPs will point to the same domain name, even if they are different sites.
- Protocol:
- Http
- Https (+$*)
- Host Name: ___________
- Port: 80
- Path: (Default /)
- Specify by:
- Advanced Config
- Request Interval
- Standard 30
- Fast (10 seconds) (+$*)
- Failure threshold: ____
- Number of consecutive failures before marking ‘down’
- String matching: Yes (+$*) / No
- If Yes, must be located within first 5120 characters
- Between 1 – 255 characters
- Latency graphs: [ ] displays on health check page (+$*)
- Invert health check status: [ ] (if you find the text and want to mark it ‘down’, i.e. “could not connect to database”
- Health checker regions: select from list of locations.
- Request Interval
| End Point / Check type | Cost per check per month |
| Basic check | $.50 |
| (+$*) AWS | $1 |
| (+$*) Non-AWS | $2 |
Create health check – Step 2: Get notified
- Create alarm: Yes / No (YES!!)
- CloudWatch then sends notification via SNS
- Send notification to:
- Existing SNS Topic
- New Topic
- Topic Name: _____________
- Email address: __________
- Separate multiple addresses by comma, semicolon or space