AWS Lambda now supports Internet Protocol Version 6 (IPv6) endpoints for inbound connections
AWS Lambda now supports IPv6 endpoints for inbound connections, allowing customers to invoke Lambda functions over IPv6. This helps customers to meet IPv6 compliance requirements, and removes the need for expensive networking equipment to handle address translation between IPv4 and IPv6.
AWS Lambda now supports IPv6 endpoints for inbound connections, allowing customers to invoke Lambda functions over IPv6. This helps customers to meet IPv6 compliance requirements, and removes the need for expensive networking equipment to handle address translation between IPv4 and IPv6.
To use this new capability, configure your applications to use AWS Lambda’s new dual-stack endpoints which support both IPv4 and IPv6. AWS Lambda’s new dual-stack endpoints have the format lambda.region.api.aws. For example, the dual-stack endpoint in US East (N. Virginia) is lambda.us-east-1.api.aws. When you make a request to a dual-stack Lambda endpoint, the endpoint resolves to an IPv6 or an IPv4 address, depending on the protocol used by your network and client.
To connect programmatically to an AWS service, you can specify an endpoint in AWS CLI or AWS SDK. For more information on service endpoints, see AWS Service endpoints. To learn more about Lambda’s service endpoints, see AWS Lambda service endpoints in the AWS documentation.
You can use AWS Lambda’s new dual-stack endpoints for inbound connections at no additional cost. The new dual-stack endpoints are generally available in US East (N. Virginia), US West (N. California), US East (Ohio), US West (Oregon), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Europe (Milano), Asia Pacific (Singapore), Asia Pacific (Tokyo), Asia Pacific (Sydney), Asia Pacific (Seoul), Asia Pacific (Osaka), Asia Pacific (Mumbai), Asia Pacific (Hong Kong), Canada (Central), Middle East (Bahrain), South America (Sao Paulo), and Africa (Cape Town). For more information on availability, please see the AWS Region table.