EC2 should be configured to use AWS VPC endpoints created for the Amazon EC2 service

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.


This check verifies the presence of a service endpoint for Amazon EC2 within each VPC. It registers a failure if a VPC does not have an Amazon EC2 service endpoint created.

This evaluation is limited to resources within a single AWS account and cannot assess resources across multiple accounts. Consequently, AWS Config and Security Hub reports FAILED findings for VPCs shared across accounts. Security Hub suggests suppressing these FAILED findings.

Enhance the security of your VPC by configuring Amazon EC2 to use an interface VPC endpoint. These endpoints leverage AWS PrivateLink technology to enable private access to Amazon EC2 API operations, ensuring that all network traffic between your VPC and Amazon EC2 remains on the Amazon network. Keep in mind that interface endpoints are only supported within the same region and cannot be established between a VPC and a service in a different region, thus preventing inadvertent Amazon EC2 API calls to other regions.

For further information on setting up VPC endpoints for Amazon EC2, refer to the Amazon EC2 User Guide for Linux Instances.


For instructions on establishing an interface endpoint to Amazon EC2 via the Amazon VPC console, refer to the Create a VPC endpoint section in the AWS PrivateLink Guide. When specifying the Service name, select com.amazonaws.region.ec2.

Additionally, you have the option to create and link an endpoint policy to your VPC endpoint to manage access to the Amazon EC2 API. To learn how to craft a VPC endpoint policy, consult the Create an endpoint policy section in the Amazon EC2 User Guide for Linux Instances.