Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the 404 HttpCode from 2019-fargate-api.yaml #254

Open
MikeTheCanuck opened this issue Jul 27, 2019 · 0 comments
Open

Remove the 404 HttpCode from 2019-fargate-api.yaml #254

MikeTheCanuck opened this issue Jul 27, 2019 · 0 comments
Labels
good first issue Good for newcomers

Comments

@MikeTheCanuck
Copy link
Contributor

Currently, to continue testing the 2019 Sandbox API container image in ECS deployment, we've had to enable the ALB Health Check to consider a "404" HTTP response as a healthy container response.

Once we've figured out what's wrong here (container, CloudFormation, whatever it turns out to be) we will remove this as a "healthy" container response, so that incremental deploys of container image builds don't replace a working container with a broken one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant