AWS eks high security documentation change
Summary
Corrected ARN formatting examples and expanded IAM policy configuration for confused deputy prevention
Security assessment
Fixes critical ARN syntax errors in security policies and provides explicit policy examples. Incorrect ARNs could lead to misconfigured resource permissions enabling cross-service attacks. Directly strengthens documentation about preventing confused deputy vulnerabilities.
Diff
diff --git a/eks/latest/userguide/cross-service-confused-deputy-prevention.md b/eks/latest/userguide/cross-service-confused-deputy-prevention.md index 5b7fb87d1..952dc3400 100644 --- a//eks/latest/userguide/cross-service-confused-deputy-prevention.md +++ b//eks/latest/userguide/cross-service-confused-deputy-prevention.md @@ -13 +13 @@ To contribute to this user guide, choose the **Edit this page on GitHub** link t -The confused deputy problem is a security issue where an entity that doesn’t have permission to perform an action can coerce a more-privileged entity to perform the action. In AWS, cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the <emphasis>calling service</emphasis>) calls another service (the <emphasis>called service</emphasis>). The calling service can be manipulated to use its permissions to act on another customer’s resources in a way it should not otherwise have permission to access. To prevent this, AWS provides tools that help you protect your data for all services with service principals that have been given access to resources in your account. +The confused deputy problem is a security issue where an entity that doesn’t have permission to perform an action can coerce a more-privileged entity to perform the action. In AWS, cross-service impersonation can result in the confused deputy problem. Cross-service impersonation can occur when one service (the _calling service_) calls another service (the _called service_). The calling service can be manipulated to use its permissions to act on another customer’s resources in a way it should not otherwise have permission to access. To prevent this, AWS provides tools that help you protect your data for all services with service principals that have been given access to resources in your account. @@ -27 +27 @@ Use `aws:SourceAccount` to let any resource in that account be associated with t -The most effective way to protect against the confused deputy problem is to use the `aws:SourceArn` global condition context key with the full ARN of the resource. If you don’t know the full ARN of the resource or if you are specifying multiple resources, use the `aws:SourceArn` global context condition key with wildcard characters (` ****`) for the unknown portions of the ARN. For example, ` arn:aws: `servicename`:`. +The most effective way to protect against the confused deputy problem is to use the `aws:SourceArn` global condition context key with the full ARN of the resource. If you don’t know the full ARN of the resource or if you are specifying multiple resources, use the `aws:SourceArn` global context condition key with wildcard characters (*) for the unknown portions of the ARN. For example, ` arn:aws:<servicename>:*:<123456789012>:*`. @@ -37 +37 @@ An Amazon EKS cluster IAM role is required for each cluster. Kubernetes clusters -The value of `aws:SourceArn` must be the ARN of an EKS cluster in the format ` arn:aws::eks:`region`:`account`:cluster/`cluster-name` `. For example, ` arn:aws::eks:us-east-1:123456789012:cluster/my-cluster` . +The value of `aws:SourceArn` must be the ARN of an EKS cluster in the format ` arn:aws:eks:`region`:`account`:cluster/`cluster-name` `. For example, ` arn:aws:eks:us-west-2:123456789012:cluster/my-cluster` . @@ -46 +46,10 @@ The following example shows how you can use the `aws:SourceArn` and `aws:SourceA - "Statement": :[.replaceable]123456789012:cluster/[.replaceable]`my-cluster`" + "Statement": [ + { + "Effect": "Allow", + "Principal": { + "Service": "eks.amazonaws.com" + }, + "Action": "sts:AssumeRole", + "Condition": { + "ArnLike": { + "aws:SourceArn": "arn:aws:eks:us-west-2:123456789012:cluster/my-cluster"