Open StephenKing opened 3 years ago
danehlim
commented
7 months ago A workaround is available for those who urgently need this functionality while this feature request is still pending. The workaround is detailed in this comment: https://github.com/aws/amazon-ecs-ami/issues/170#issuecomment-1830517333
dali546
commented
5 months ago Hi @StephenKing, I have submitted this PR a while ago. It does what's asked in this feature.
I know this is still in the proposed phase, but can this issue be pushed along as the work to include the package is already done.
Currently I am using Userdata to install this package, but this sometimes fails, leading to misconfigured instances being launched. If this package was included in the AMI, it would greatly improve our stability
dali546
commented
5 months ago cc @StephenKing @danehlim @chienhanlin @amogh09 @hyandell anyone???
tamuanand
commented
4 months ago This feature request has been in place since Mar 2021 - around 3 years now.
How long does this remain a feature request and actually become a feature (which will be a huge boon)
neilferreira
commented
3 months ago +1 on this.
Community Note
Tell us about your request Include ec2-instance-connect in the ECS-optimized AMIs
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? We are migrating to use SSM + ec2-instance-connect for management of EC2 instances. If this would be included in ECS-optimized images in the same way as it is for other provided images, there would be no gap when accessing the EC2 instance of an ECS cluster.
Are you currently working around this issue? Falling back to SSM Session Manager only, alternatively baking our own AMIs