thoughtbot / thoughtbot/flightdeck
Route53 Health Checks for Ingress
Open
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 100
- Forks
- 11
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 3
Description
We're using NewRelic monitoring for health checks, which sometimes can be inaccurate for low traffic sites.
Route53 has their own free health check for AWS services, so we can add that to the ingress setup.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Terraform ingress setup and its existing NewRelic health-check configuration. Review the AWS Route53 health-check requirements and determine how the check should be represented in the ingress modules; done means the ingress uses a Route53 health check for AWS services instead of relying only on NewRelic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, terraform
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100