- 最新
- 最多得票
- 最多評論
Systems Manager requires three VPC endpoints to be fully managed:
https://repost.aws/knowledge-center/ec2-systems-manager-vpc-endpoints
com.amazonaws.[region].ssm
com.amazonaws.[region].ec2messages
com.amazonaws.[region].ssmmessages
Hello.
Please share the VPC endpoint you configured.
Also, check whether the security group configured for the VPC endpoint allows HTTPS.
https://docs.aws.amazon.com/systems-manager/latest/userguide/setup-create-vpc.html
Systems Manager requires three VPC endpoints to be fully managed: https://repost.aws/knowledge-center/ec2-systems-manager-vpc-endpoints
com.amazonaws.[region].ssm com.amazonaws.[region].ec2messages com.amazonaws.[region].ssmmessagesIf you are only using Session Manager, you will be fine with the following VPC endpoint.
com.amazonaws.[region].ssm com.amazonaws.[region].ssmmessages
Sure,
Endpoint Type: Interface. Service Name: com.amazonaws.us-east-1.ssm.
please let me know if you need anything else.
No, no and no, type=Interface is known after the fact. You need to explicit the Service Category that the wizard actually offers please. AWS services | EC2 Instance Connect | Private Link | Other endpoint services | AWS Marketplace services (not that one, for the completeness' sake)
Yes, we do need to know what Outbound Rules are needed for that SG that protects the VPC endpoint, as that part is not very clear. Inbound is made clear in doco (HTTPS 443 / VPC CIDR), but not Outbound. Also, is Inbound considered as "exiting out of VPC onto AWS general services?"
相關內容
- 已提問 6 個月前
- 已提問 6 個月前
AWS 官方已更新 1 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
Thank you, that fixed the issue.