Amazon EMR on EKS now supports Amazon EKS Pod Identity

Today, Amazon EMR on EKS announces support for [Amazon EKS Pod Identity](https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html), simplifying the setup of IAM permissions required by EMR on EKS jobs to access other AWS resources. With this launch, you can configure IAM permissions through a single API call, significantly reducing complexity and potential for errors. The new feature also allows you to leverage IAM roles across multiple clusters without the need to update IAM trust policies for use in new clusters, improving reusability and operational efficiency. To run workloads on Amazon EMR on EKS, customers need to create a job execution IAM role that pods in EKS cluster will use to interact with other AWS resources such as Amazon S3 buckets. Previously, customers had to perform multiple configuration steps such as creating an [OIDC](https://docs.aws.amazon.com/IAM/latest/UserGuide/id%5Froles%5Fproviders%5Fcreate%5Foidc.html) identity provider and updating IAM’s role trust policy. Role trust policy size also limited the number of EKS clusters that customers could reuse a job execution role across. Now, customers can configure IAM permissions through a single API call and reuse an IAM role across multiple clusters without additional configuration updates. Amazon EMR on EKS support for EKS Pod Identity is available in all Regions where Amazon EMR on EKS is currently available, except the China Regions. To get started visit the [documentation](https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/setting-up-enable-IAM.html).