AWS eks high security documentation change
Summary
Fixed grammatical errors and clarified warnings about terminating control-plane instances during updates
Security assessment
The changes strengthen warnings about accidental termination of Kubernetes control-plane instances, which could cause service disruption or data loss. Explicitly stating that terminating instances risks cluster availability and data loss constitutes concrete security-related guidance.
Diff
diff --git a/eks/latest/userguide/eks-outposts-troubleshooting.md b/eks/latest/userguide/eks-outposts-troubleshooting.md index d1de7238f..9941c4766 100644 --- a//eks/latest/userguide/eks-outposts-troubleshooting.md +++ b//eks/latest/userguide/eks-outposts-troubleshooting.md @@ -17 +17 @@ This topic covers some common errors that you might see while using local cluste -Never terminate any managed EKS local cluster `Kubernetes` control-plane instance running on Outpost unless explicitly instructed by AWS Support. Terminating these instances impose a risk to local cluster service availability, including loss of the local cluster in case multiple instances are simultaneously terminated. EKS local cluster `Kubernetes` control-plane instances are identified by the tag `eks-local:controlplane-name` on the EC2 instance console. +Never terminate any managed EKS local cluster `Kubernetes` control-plane instance running on Outpost unless explicitly instructed by AWS Support. Terminating these instances imposes a risk to local cluster service availability, including loss of the local cluster in case multiple instances are simultaneously terminated. EKS local cluster `Kubernetes` control-plane instances are identified by the tag `eks-local:controlplane-name` on the EC2 instance console. @@ -107 +107 @@ During an automatic platform-version rollout a cluster status changes to `UPDATI -Amazon EKS ensures at least 2 out of 3 Kubernetes control-plane instances are healthy and operational cluster nodes in order to maintain the local cluster availability and prevent service interruption. If a local cluster is stalled in `UPDATING` state it is usually because there is some infrastructure or configuration issue preventing the two-instances minimum availability to be guaranteed in case the process continues. So the update process stops progressing to protect the local cluster service interruption. +Amazon EKS ensures at least 2 out of 3 Kubernetes control-plane instances are healthy and operational cluster nodes in order to maintain the local cluster availability and prevent service interruption. If a local cluster is stalled in `UPDATING` state it is usually because there is some infrastructure or configuration issue preventing the two-instances minimum availability to be guaranteed in case the process continues. So the update process stops progressing to prevent local cluster service interruption. @@ -111 +111 @@ It is important to troubleshoot a local cluster stuck in `UPDATING` status and a -Do not terminate any managed EKS local cluster `Kubernetes` instances on Outposts unless explicitly instructed by AWS Support. This is especially important for local clusters stuck in `UPDATING` state because there’s a high probability that another control-plane nodes is not completely healthy and terminating the wrong instance could cause service interruption and risk local-cluster data loss. +Do not terminate any managed EKS local cluster `Kubernetes` instances on Outposts unless explicitly instructed by AWS Support. This is especially important for local clusters stuck in `UPDATING` state because there’s a high probability that another control-plane node is not completely healthy and terminating the wrong instance could cause service interruption and risk local-cluster data loss.