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
AWS has announced a new functionality to access your containers on AWS Fargate and Amazon EC2. ECS Exec leverages AWS Systems Manager (SSM), and specifically SSM Session Manager, to create a secure channel between the device you use to initiate the “exec“ command and the target container.
Hey @luiszimmermann - this was raised a while ago in #37. I still believe that there is a good separation of concerns here, simply because of the different layers of abstraction in ECS (Clusters, Services, Tasks, Containers) vs. EC2. You can check out https://github.com/tedsmitt/ecsgo and see if that meets your needs? Happy to discuss further though!
AWS has announced a new functionality to access your containers on AWS Fargate and Amazon EC2. ECS Exec leverages AWS Systems Manager (SSM), and specifically SSM Session Manager, to create a secure channel between the device you use to initiate the “exec“ command and the target container.
Thanks in advance and thanks for this great tool
The text was updated successfully, but these errors were encountered: