AWS eks documentation change
Summary
Updated terminology from 'Amazon EKS' to 'AWS EKS' and added an explicit IAM trust policy JSON example for Pod Identity Associations, replacing a placeholder error message.
Security assessment
The change adds documentation for a security feature (Pod Identity Associations) by providing a concrete IAM trust policy. This aids in implementing secure pod identity but does not indicate a response to a specific security issue.
Diff
diff --git a/eks/latest/eksctl/pod-identity-associations.md b/eks/latest/eksctl/pod-identity-associations.md index d891bbe0d..d9aba451f 100644 --- a//eks/latest/eksctl/pod-identity-associations.md +++ b//eks/latest/eksctl/pod-identity-associations.md @@ -9 +9 @@ PrerequisitesCreating Pod Identity AssociationsFetching Pod Identity Association -Amazon EKS has introduced a new enhanced mechanism called Pod Identity Association for cluster administrators to configure Kubernetes applications to receive IAM permissions required to connect with AWS services outside of the cluster. Pod Identity Association leverages IRSA, however, it makes it configurable directly through the EKS API, eliminating the need for using IAM API altogether. +AWS EKS has introduced a new enhanced mechanism called Pod Identity Association for cluster administrators to configure Kubernetes applications to receive IAM permissions required to connect with AWS services outside of the cluster. Pod Identity Association leverages IRSA, however, it makes it configurable directly through the EKS API, eliminating the need for using IAM API altogether. @@ -23 +23,15 @@ Additionally, if using a pre-existing IAM role when creating a pod identity asso - # Error: No files found with UUID: 44d1085a-03ca-431a-9774-b786a9774200 + { + "Version":"2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Principal": { + "Service": "pods.eks.amazonaws.com" + }, + "Action": [ + "sts:AssumeRole", + "sts:TagSession" + ] + } + ] + }