-
Notifications
You must be signed in to change notification settings - Fork 519
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
Add support for ECS Exec #1649
Comments
Thanks for the request - we'll look into it! |
+1 with some fluff text context! We use ECS Exec to perform a lot of tasks from debugging to maintenance across our containers. We have multiple types of Operating Systems we use and all but Bottlerocket supports this feature. I would love to finally switch all the remaining Operating Systems we use to Bottlerocket for all the lovely benefits it brings but I can't complete that migration until this feature exists. Would love to see this happen! |
I was curious about what will be required in Bottlerocket in order to support this feature. I found out that the ECS agent will mount SSM binaries provided by the host, which I assume are statically linked. |
I just hit my head on this. Unfortunately it seems that there's no error surfaced anywhere when a task can't be scheduled because of this requirement. |
@dmitmasy fyi for your awareness and prioritization. |
ECS Exec is an important feature of ECS. It allows customers to obtain a shell in the context of a running container (à la
kubectl exec
), without requiring admin access to the host.Currently, ECS Exec is supported on the Amazon Linux 2-based ECS optimized AMI and similar variants, but is not supported on Bottlerocket. Given ECS Exec's popularity, it makes sense to add support for it in Bottlerocket as well.
The text was updated successfully, but these errors were encountered: