You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to see App Mesh implement this idea, please upvote with a 👍.
Tell us about your request
AppMesh VirtualNode health-checks should be integrated with ECS container life cycles in a similar fashion to ELB health-checks.
Which integration(s) is this request for?
ECS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Like many teams migrating to AppMesh, my team is currently migrating from an architecture using ALBs for discovery of our services. ALB target group health checks have a tight integration with ECS, which will kill and replace any tasks which fail the health checks. In AppMesh, our goal is to largely remove ALBs from our system architecture and instead rely on CloudMap for service discovery. Without ALBs, we no longer have an easy way to perform application container health checks across a large variety of operating environments. Given that one of the primary objectives of a service mesh is to abstract away networking concerns from the application and facilitate highly variable application environment micro-service architectures this feature feels like a natural fit for AppMesh. In addition, ALB target groups also provide metrics for healthy/unhealthy host counts which is something that we now lack.
The crux of the issue is due to the large variance in application container base images. debian, alpine, node, scratch, python etc all have different sets of tools installed, and even have different shells available. Because of this, using the ECS health-checks directly is non-trivial. It would involve ensuring that curl, or wget is installed on all of our container images which would be a large undertaking given that we have not needed this before now.
If AppMesh VirtualNode health-checks performed the same as target group health checks then the application container environment would once again no longer matter.
Are you currently working around this issue?
Currently, we are exploring the level of effort involved in making ECS health checks happen via curl or wget. We have hundreds of services, and modifying all of them to be compatible with this style of health-check will be a lot of work.
The text was updated successfully, but these errors were encountered:
If you want to see App Mesh implement this idea, please upvote with a 👍.
Tell us about your request
AppMesh VirtualNode health-checks should be integrated with ECS container life cycles in a similar fashion to ELB health-checks.
Which integration(s) is this request for?
ECS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Like many teams migrating to AppMesh, my team is currently migrating from an architecture using ALBs for discovery of our services. ALB target group health checks have a tight integration with ECS, which will kill and replace any tasks which fail the health checks. In AppMesh, our goal is to largely remove ALBs from our system architecture and instead rely on CloudMap for service discovery. Without ALBs, we no longer have an easy way to perform application container health checks across a large variety of operating environments. Given that one of the primary objectives of a service mesh is to abstract away networking concerns from the application and facilitate highly variable application environment micro-service architectures this feature feels like a natural fit for AppMesh. In addition, ALB target groups also provide metrics for healthy/unhealthy host counts which is something that we now lack.
The crux of the issue is due to the large variance in application container base images.
debian
,alpine
,node
,scratch
,python
etc all have different sets of tools installed, and even have different shells available. Because of this, using the ECS health-checks directly is non-trivial. It would involve ensuring that curl, or wget is installed on all of our container images which would be a large undertaking given that we have not needed this before now.If AppMesh VirtualNode health-checks performed the same as target group health checks then the application container environment would once again no longer matter.
Are you currently working around this issue?
Currently, we are exploring the level of effort involved in making ECS health checks happen via curl or wget. We have hundreds of services, and modifying all of them to be compatible with this style of health-check will be a lot of work.
The text was updated successfully, but these errors were encountered: