[ECS] [request]: Unable to use ECS Exec on restarted containers

[an-hato]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
Unable to use ECS Exec on containers restarted by container restart policy

Which service(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?
When attempting to use ECS Exec on containers that have been restarted by the container restart policy, connection fails with a TargetNotConnectedException.
The connection is successful if the task is recreated.

Are you currently working around this issue?
No, there is no way to connect to restarted containers.

Additional context
There is related documentation available at the following link:

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container-restart-policy.html
https://blog.serverworks.co.jp/container_restart#%E6%B3%A8%E6%84%8F%E4%BA%8B%E9%A0%85

Attachments
No attachments are included.