3 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi,
It's not a direct reponse to your question but it may help you get the answer: AWS has open-sourced the scripts used to build the Amazon ECS-optimized Linux AMIs.
See https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-ami-build-scripts.html
Those scripts are available at https://github.com/aws/amazon-ecs-ami
By analyzing them, you will see if they contain any settings preventing the use of EC2 Instance Connect Endpoint. You can also adapt them to your specific needs (and make sure that you can have ssh connection)
Best,
Didier
0
Hi,
Please check 2 things:
- If VPC of EC2 Instance Connect Endpoint is the same as EC2 VPC.
- Check SG of EC2 Instance Connect Endpoint. SG EC2 Instance Connect Endpoint should allow SSH TCP 22 for outbound traffic. SG of EC2 should have inbound rule that allows SG of EC2 Instance Connect Endpoint.
répondu il y a 5 mois
0
Hey!
All this seems to work. Again, I am testing with the same VPC and SG, and I get it working with a different AMI. But for some reason, it does not work with the ECS AMI.
répondu il y a 5 mois
Contenus pertinents
- demandé il y a 5 mois
- demandé il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 6 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans