AWS eks medium security documentation change
Summary
Changed IAM policy condition keys from aws:PrincipalTag to aws:RequestTag for EKS pod identity assignments
Security assessment
Switching from PrincipalTag to RequestTag changes the authorization context to validate tags provided in the request rather than tags attached to the principal. This prevents potential privilege escalation scenarios where existing principal tags might be reused improperly, making it a security-hardening change. The AWS documentation explicitly states this is part of establishing 'a secure trust chain'.
Diff
diff --git a/eks/latest/userguide/pod-id-assign-target-role.md b/eks/latest/userguide/pod-id-assign-target-role.md index 030336fdc..ed91cc75a 100644 --- a//eks/latest/userguide/pod-id-assign-target-role.md +++ b//eks/latest/userguide/pod-id-assign-target-role.md @@ -87,3 +87,3 @@ In this step, you will establish a secure trust chain by creating and configurin - "aws:PrincipalTag/eks-cluster-arn": "arn:aws:eks:us-east-1:111122223333:cluster/example-cluster", - "aws:PrincipalTag/kubernetes-namespace": "ExampleNameSpace", - "aws:PrincipalTag/kubernetes-service-account": "ExampleServiceAccountName" + "aws:RequestTag/eks-cluster-arn": "arn:aws:eks:us-east-1:111122223333:cluster/example-cluster", + "aws:RequestTag/kubernetes-namespace": "ExampleNameSpace", + "aws:RequestTag/kubernetes-service-account": "ExampleServiceAccountName"