AWS Lambda now supports AWS PrivateLink in previously unsupported Availability Zones

AWS Lambda now supports AWS PrivateLink in previously unsupported Availability Zones in US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Mumbai), South America (São Paulo), Canada (Central), and EU (London) regions. With this launch, AWS Lambda now supports AWS PrivateLink in all Availability Zones in all commercial regions, AWS GovCloud (US-East), and AWS GovCloud (US-West).

Previously, AWS Lambda supported AWS PrivateLink in all Availability Zones in US East (Ohio), US West (N. California), Asia Pacific (Hong Kong), Asia Pacific (Sydney), Asia Pacific (Osaka), EU (Frankfurt), EU (Ireland), EU (Milano), EU (Paris), EU (Stockholm), Middle East (Bahrain), AWS GovCloud (US-East), AWS GovCloud (US-West), and Africa (Cape Town). With this feature you can manage and invoke Lambda functions from your Amazon Virtual Private Cloud (VPC) without exposing your traffic to the public internet. PrivateLink provides private connectivity between your VPCs and AWS services such as Lambda, on the private AWS network.

With PrivateLink, you can provision and use VPC endpoints to access the Lambda API from your VPC. VPC endpoints deliver private and reliable connectivity to Lambda without requiring Internet Gateway, Network Address Translation (NAT) devices, or firewall proxies. You can attach AWS Identity and Access Management (IAM) policies to your VPC endpoint to control who can use the VPC endpoint and which functions can be accessed from that VPC endpoint.

For more information, see the AWS Region table. For complete information on pricing for VPC endpoints, please refer to the AWS PrivateLink pricing page. You can get started by creating a VPC endpoint for Lambda using AWS Management Console, AWS CLI, or AWS CloudFormation. To learn more, visit Lambda developer guide.