1 Answer
- Newest
- Most votes
- Most comments
-2
The bug: if you change anything (or nothing) in the configuration using the console GUI, App Runner will silently change the HTTP endpoint to /
!
Perhaps the log statement thinks printing out /
is redundant, but it is not because the log message appears identical to the original default TCP check.
I got around this issue by adding a redundant health check on /
.
answered 2 years ago
I'm facing the same issue, is there a way for using the custom health check config instead of adding a redundant?
Relevant content
- asked a year ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
We're experiencing the same issue.
Have a healthcheck set to /health, all working ok when there's an image update deployment. But if a user changes an env var via the console it results in a rollback deploy as it's hitting / for healthchecking.