AWS Config Now Supports AWS PrivateLink
Starting today, AWS Config supports AWS PrivateLink, which enables you to route data between your Amazon Virtual Private Cloud (VPC) and AWS Config without exposing your VPC subnets to the Internet.
Starting today, AWS Config supports AWS PrivateLink, which enables you to route data between your Amazon Virtual Private Cloud (VPC) and AWS Config without exposing your VPC subnets to the Internet.
AWS Config is a service that enables you to assess, audit, and evaluate the configurations of your AWS resources. AWS Config continuously monitors and records your AWS resource configurations and enables you to automate the evaluation of recorded configurations against desired configurations. By using AWS Config with Amazon VPC endpoints, your VPC resources can communicate with AWS Config within the AWS network, which helps you meet your compliance and regulatory requirements to limit public internet connectivity.
Support for AWS PrivateLink is available in US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), Canada (Central), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), EU (Frankfurt), EU (Ireland), EU (London), EU (Paris), and South America (Sao Paulo) Regions. To see the full list of supported AWS Regions, see AWS Regions and Endpoints in the AWS General Reference.
For more information about PrivateLink, see Accessing Services Through AWS PrivateLink in the Amazon VPC User Guide. For more information about how to create a VPC endpoint, see Interface VPC Endpoints (AWS PrivateLink) in the Amazon VPC User Guide.
For more information about AWS Config, see: