Amazon Lambda now supports inbound IPv6 connectivity over Amazon PrivateLink
Amazon Lambda now supports IPv6-only and dual-stack PrivateLink interface VPC Endpoints, enabling you to access the Lambda API without traversing the public internet or being constrained by the limited number of IPv4 addresses in your VPC. Amazon PrivateLink is a highly available, scalable service that allows you to privately connect your VPC to services and resources as if they were in your VPC.
Previously, Lambda supported inbound private connectivity over PrivateLink using IPv4-only VPC endpoints. With today’s launch, we are expanding Lambda’s inbound private connectivity to include IPv6-only and dual-stack VPC endpoints, enabling you to invoke and manage Lambda functions over IPv6 from dual-stack or IPv6-only VPCs. This launch combines the benefits of private connectivity with the larger address space and simpler network configuration of the IPv6 protocol.
Amazon Lambda supports inbound IPv6 connectivity in Amazon Web Services China (Beijing) Region, operated by Sinnet and Amazon Web Services China (Ningxia) Region, operated by NWCD. For more information on availability, see the Amazon Web Services Region table. Please refer to PrivateLink Pricing for price of using VPC endpoints. You can get started by creating a VPC endpoint for Lambda using the Amazon Web Services Management Console, Amazon CLI, Amazon CDK, Amazon CloudFormation and the Amazon SDK. To learn more, visit the Lambda developer guide.