All news with #ipv6 tag

AWS Kinesis Data Streams Adds IPv6 and FIPS in GovCloud

🌐 Amazon Web Services announced that Kinesis Data Streams now supports API requests over IPv6 in the AWS GovCloud (US) Regions, with optional dual-stack (IPv4/IPv6) public and VPC endpoints. The new endpoints have been validated under FIPS 140-3, enabling FIPS-compliant encryption for customers contracting with the US federal government. IPv6 support reduces address overlap and simplifies connectivity for devices and networks already using IPv6. This capability is available in all Regions where Kinesis Data Streams operates, including GovCloud and China Regions.

AWS Step Functions Adds IPv6 Dual-Stack Endpoint Support

🌐 AWS Step Functions now supports IPv6 via new dual-stack IPv4/IPv6 endpoints, enabling customers to send IPv6 traffic directly to the service. The enhancement preserves backwards compatibility with existing IPv4 endpoints and enables PrivateLink interface VPC endpoint connectivity so workloads can access Step Functions privately without traversing the public internet. IPv6 support is generally available in several US commercial and GovCloud regions.

AWS Elastic Beanstalk Adds IPv6 Dual-Stack Load Balancers

🌐 AWS Elastic Beanstalk now supports dual-stack configuration for Application Load Balancers (ALB) and Network Load Balancers (NLB). By setting the IpAddressType option to dualstack, Elastic Beanstalk automatically configures your load balancer to serve both IPv4 and IPv6 and creates corresponding A and AAAA DNS records. Existing IPv4 environments can be upgraded to dual-stack or reverted back as needed. The feature is available in all AWS regions that support Elastic Beanstalk and ALB/NLB and simplifies deployment to IPv6-only networks while retaining IPv4 compatibility.

Amazon CloudFront Adds IPv6 Origin Connectivity Support

🌐 Amazon CloudFront now supports IPv6 connectivity to origin servers, enabling end-to-end IPv6 content delivery for web applications. Customers can configure custom origins as IPv4-only (default), IPv6-only, or dual-stack; in dual-stack mode CloudFront will automatically balance requests across IPv4 and IPv6 addresses. IPv6 origin support is available in all supported AWS Commercial Regions and excludes Amazon S3 and VPC origins. This capability can improve performance for native IPv6 users and reduce pressure from IPv4 address exhaustion for origin infrastructure.

Amazon RDS Proxy Adds IPv6 Support for Connections

🌐 Amazon RDS Proxy now supports IPv6 addresses for pooling and sharing database connections, while continuing to offer existing IPv4 endpoints for backwards compatibility. Customers may specify proxy target connections using either IPv4 or IPv6. The change reduces the need to manage overlapping VPC address spaces and helps mobile, IoT, and modern serverless applications that open many database connections. By pooling connections, RDS Proxy improves database efficiency and application scalability.

DNS64 and NAT64 for Connecting IPv6-only Workloads

🌐 Google Cloud introduces DNS64 and NAT64 for Cross‑Cloud Network to allow IPv6-only workloads to access IPv4-only services without dual‑stack. DNS64 synthesizes AAAA responses by embedding IPv4 addresses into the 64:ff9b::/96 prefix, and NAT64 translates traffic by extracting those addresses and initiating IPv4 connections on behalf of IPv6 clients. The blog post includes step‑by‑step gcloud commands to create VPCs, DNS64 policies, and a NAT64 gateway.

AWS Control Tower Adds IPv6 Support Across Regions

🌐 AWS Control Tower and the Control Catalog APIs now accept IPv6 addresses through dual‑stack public endpoints, enabling connections over IPv6, IPv4, or both. The existing IPv4-only endpoints remain available for backwards compatibility. Support is available in all Regions where Control Tower and Control Catalog are offered, helping reduce overlapping address space in Amazon VPCs as IPv6 adoption grows. Customers should consult AWS guidance and the IPv6 on AWS whitepaper for configuration and best practices.

RDS Data API Now Supports IPv6 Dual-Stack Connectivity

🌐 RDS Data API now supports IPv6 with dual-stack (IPv4/IPv6) connectivity for Aurora databases, enabling expanded address space and simplified migration from IPv4. The capability is available in all commercial AWS regions where Data API is offered, except Canada (Central). IPv6 lets you assign contiguous IP ranges to microservices and scale beyond VPC IPv4 limits while retaining IPv4 connectivity during transition. Data API continues to pool connections and integrates with AWS AppSync GraphQL; consult the documentation for endpoint and network configuration guidance.

AWS App Runner Adds IPv6 for Inbound and Outbound Traffic

🌐 AWS App Runner now supports IPv6 for both inbound and outbound traffic on public and private service endpoints. This removes the need for IPv4/IPv6 address translation and helps customers meet IPv6 compliance requirements. You enable the capability by selecting the dual-stack option in the networking configuration for new or existing services. IPv6 support is available in all Regions where App Runner is offered.

AWS Client VPN Adds Connectivity for IPv6 Resources

🔒 AWS Client VPN now supports secure remote access to IPv6-enabled VPC resources, allowing administrators to connect remote users and devices directly to IPv6 workloads. Administrators can deploy IPv6-only or dual-stack Client VPN endpoints to preserve end-to-end IPv6 connectivity and simplify network design for organizations adopting IPv6. This capability expands prior IPv4-only support and helps meet IPv6 adoption and compliance goals. The feature is generally available in all Client VPN regions except Middle East (Bahrain) and is provided at no additional cost, with IPv6 and dual-stack endpoints billed at the existing per-hour endpoint rate.