AWS eks documentation change
Summary
Updated terminology from 'isolation boundary' to 'compute boundary' and GitHub path
Security assessment
Clarifies Fargate's security model but does not resolve a specific security flaw. The note about IMDS reinforces security practices.
Diff
diff --git a/eks/latest/userguide/fargate.md b/eks/latest/userguide/fargate.md index f5fd0ddfc..80e1c749f 100644 --- a//eks/latest/userguide/fargate.md +++ b//eks/latest/userguide/fargate.md @@ -1 +1 @@ -[](/pdfs/eks/latest/userguide/eks-ug.pdf#fargate "Open PDF")[](https://github.com/awsdocs/amazon-eks-user-guide/tree/mainline/latest/ug/nodes/fargate.xml "Edit this page on GitHub") +[](/pdfs/eks/latest/userguide/eks-ug.pdf#fargate "Open PDF")[](https://github.com/awsdocs/amazon-eks-user-guide/tree/mainline/latest/ug/nodes/fargate.adoc "Edit this page on GitHub") @@ -23 +23 @@ Here are some things to consider about using Fargate on Amazon EKS. - * Each Pod that runs on Fargate has its own isolation boundary. They don’t share the underlying kernel, CPU resources, memory resources, or elastic network interface with another Pod. + * Each Pod that runs on Fargate has its own compute boundary. They don’t share the underlying kernel, CPU resources, memory resources, or elastic network interface with another Pod.