AWS eks medium security documentation change
Summary
Added note about physical access implications when creating local clusters on RAM-shared Outposts
Security assessment
Explicitly highlights physical security risk ('places control plane under Outpost owner's physical access'), which is a security consideration for shared infrastructure
Diff
diff --git a/eks/latest/userguide/eks-outposts.md b/eks/latest/userguide/eks-outposts.md index 2b154e017..a372a9c9b 100644 --- a//eks/latest/userguide/eks-outposts.md +++ b//eks/latest/userguide/eks-outposts.md @@ -87 +87,6 @@ Troubleshooting | See [Troubleshoot problems with Amazon EKS clusters and nodes -On EC2 instance store Outposts, IRSA and EKS Pod Identity depend on AWS STS in the AWS Region. During network disconnects, workloads that use IRSA or Pod Identity cannot obtain new credentials. For more information, see [Prepare local Amazon EKS clusters on AWS Outposts configured with EC2 instance store for network disconnects](./eks-outposts-instance-store-network-disconnects.html). + * Creating a local cluster on a RAM-shared Outpost places the cluster’s control plane under the Outpost owner’s physical access + + * On EC2 instance store Outposts, IRSA and EKS Pod Identity depend on AWS STS in the AWS Region. During network disconnects, workloads that use IRSA or Pod Identity cannot obtain new credentials. For more information, see [Prepare local Amazon EKS clusters on AWS Outposts configured with EC2 instance store for network disconnects](./eks-outposts-instance-store-network-disconnects.html). + + +