[v2] [customization] Create/delete role associations for EMR on EKS #9254
+2,159
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
EKS Pod Identity requires users to create pod identity associations for cluster service accounts that the pod container is going to use with a configured job execution IAM role. This requires users to provide service account names and the IAM role arn. However, service account information is opaque in the EMR on EKS service so the
--create-role-associations
and--delete-role-associations
customizations simplify management by resolving the correct service accounts based on the input cluster and role names.Manual testing
Create an IAM role with the following assume role policy document:
Create an EKS cluster.
Run the create command, replacing the
my-cluster
andmy-role
values:Run the delete command, replacing the
my-cluster
andmy-role
values: