New feature

Amazon EMR Serverless now supports IPv6 and dual-stack connectivity

Amazon EMR Serverless now supports IPv6 and dual-stack connectivity, expanding beyond IPv4-only connectivity and maintaining backward compatibility with existing IPv4 workloads.

Amazon EMR Serverless now supports IPv6 and dual-stack connectivity, extending traditional IPv4-only connections. Jobs for Apache Spark and Apache Hive can run within Amazon VPC using IPv6, dual-stack (IPv4 and IPv6), or IPv6-only subnets. This increases flexibility for connecting to data stores and services while maintaining full backward compatibility with existing IPv4 workloads. As Spark and Hive workloads scale to many workers, organizations face constraints on VPC and subnet IPv4 address space and compliance requirements mandating IPv6 adoption. Dual-stack connectivity allows EMR Serverless applications to support both IPv4 and IPv6, maintaining backward compatibility with existing IPv4 workloads while gradually adopting IPv6. Using IPv6-only subnets avoids IPv4 address exhaustion and enables job access to IPv6 endpoints and services inside and outside the VPC. IPv6 and dual-stack connectivity for Amazon EMR Serverless are available in all AWS regions where EMR Serverless is offered, at no additional cost, and are supported in all EMR Serverless release versions. For more information, see "Configuring IPv6 Subnets for EMR Serverless Applications" and "Configuring VPC Access for EMR Serverless Applications".

Why it matters

This change affects users who need to run Apache Spark and Apache Hive workloads over IPv6. It addresses IPv4 address space constraints and compliance requirements within VPCs.

Regions: Same as Amazon EMR Serverless

Read the original AWS announcement