updated the CloudFormation Stack with proper health checks #495
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@all-contributors please add @pitthecat pitthecat for infrastructure |
|
I've put up a pull request to add @pitthecat! 🎉 |
|
Awesome @pitthecat, thanks you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there, I updated the health checks in the CloudFormation stack as they were a bit cumbersome.
/.well-known/apollo/server-healthas health path -> you get HTTP 200 as return value which is way more intuitive matcher than 400 :)/pingwhich allows the usage of HTTP 200 as matcherI increased
HealthCheckIntervalSecondsto 15 seconds. This is more than enough and you have less log entries with simple health check GET requests in AWS Cloudwatch. I deployed the improved health checks on my cluster today and they work fine.