Adding Container Health Check

[henriquesantanati]

In order to replace unhealthy tasks, Task Definition needs to have the Container Health Check configured for Service Discovery service.

Description

As per AWS Docs:

We recommend you use container-level health checks managed by Amazon ECS for your service discovery service. HealthCheckCustomConfig—Amazon ECS manages health checks on your behalf. Amazon ECS uses information from container and health checks, and your task state, to update the health with AWS Cloud Map. This is specified using the --health-check-custom-config parameter when creating your service discovery service. For more information, see HealthCheckCustomConfig in the AWS Cloud Map API Reference.

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• [X] Understand the repository structure
• [X] Add yourself as an author
• [X] Add your pattern
• [X] Add a great SVG diagram for your pattern
• [X] Read our general contribution guidelines
• [X] Read our code of conduct
• [X] Confirm your pattern frontmatter lints correctly. i.e. run npm install && npm run lint locally from your dev environment

[containers-aws-bot]

container-patterns PR Release triggered by henriquesantanati

👋 Thank you for your PR! Preview environment release has started. This conversation will be updated with a preview URL soon.

🔗 Link to Action run

Commit ref: main Commit sha: 8b1a06982ba44fdca697e1cd917bbe7523bd0ec9

✅ Release succeeded

🔗 Link to Preview URL

[containers-aws-bot]

container-patterns PR Release triggered by henriquesantanati

👋 Thank you for your PR! Preview environment release has started. This conversation will be updated with a preview URL soon.

🔗 Link to Action run

Commit ref: main Commit sha: bb3d96b3d5465934158ee0ebaf93476fe896fb3f

✅ Release succeeded

🔗 Link to Preview URL

[containers-aws-bot]

📄 PR has been closed.

✅ The Amplify preview environment has been removed. ✅ Working branch has been deleted according to policy.