Amazon EMR on EKS now supports IPv6 Amazon EKS clusters
Amazon EMR on EKS now supports running workloads on IPv6 Amazon EKS clusters, enabling large-scale Spark and Flink workloads to scale using the expanded IPv6 address space
Today, AWS announced Amazon EMR on EKS now supports running workloads on IPv6 Amazon Elastic Kubernetes Service (Amazon EKS) clusters. Amazon EMR on EKS enables running open-source big data frameworks like Apache Spark and Apache Flink on Amazon EKS. IPv6 support allows large teams to utilize IPv6's expansive address space as analysis workloads grow, eliminating the need for secondary CIDR ranges or prefix delegation to bypass IPv4 address limits. Large jobs, such as Spark jobs with 500 executors, can run concurrently without addressing constraints. Workloads can be submitted via StartJobRun, Spark Connect Interactive Endpoints, and Amazon SageMaker Unified Studio, with no additional configuration required, and Flink, Livy, and Spark operators are also supported. This feature is available from Amazon EMR releases emr-7.14.0 and emr-spark-8.0.0 at no extra cost, and IPv6 cluster support is available in all AWS regions where Amazon EMR on EKS and IPv6 Amazon EKS clusters are offered.
Why it matters
This update affects data platform and analytics teams running large-scale analytics workloads. The expanded IPv6 address space allows them to scale workloads without addressing limitations.