admin管理员组

文章数量:1406063

In aws I created a t3.nano aws-linux ec2 instance. Attached an instance profile with the following policies:

- AmazonEC2RoleforSSM
- AmazonSSMFullAccess
- AmazonSSMManagedEC2InstanceDefaultPolicy
- AmazonSSMManagedInstanceCore

The instance is in my vpc, in a private subnet. The private subnet route table is 10.0.0.0/16 local (no igw no nat gateway).

The instance's security group is also in the same vpc with following inbound/outbouns rules:

inbound: https port 443 0.0.0.0/0 ssh port 22 0.0.0.0/0

outbound: https port 443 0.0.0.0/0

I have created the following VPC endpoints on the same vpc and security group as the ec2:

- com.amazonaws.us-east-1.ssm
- com.amazonaws.us-east-1.ssmmessages
- com.amazonaws.us-east-1.ec2messages

Now, I am trying to connect to my instance via session manager. For that I need to start a session, but I don't see my EC2 in the target instances.

What could be the reason for that?

After VPC endpoints creation, do I need somehow to associate them to with instance?

本文标签: amazon web servicesAWS EC2 in Private Subnet Not Appearing in SSM Session ManagerStack Overflow