AWS eks documentation change

Service: eks · 2025-08-25 · Documentation low

File: eks/latest/best-practices/subnets.md

Summary

Removed section about using AWS Cloud9 to access private clusters including associated image and blog link

Security assessment

Content removal of deprecated access method documentation. No security implications - only removes guidance rather than addressing vulnerabilities.

Diff

diff --git a/eks/latest/best-practices/subnets.md b/eks/latest/best-practices/subnets.md
index 1d545633d..5214d569d 100644
--- a//eks/latest/best-practices/subnets.md
+++ b//eks/latest/best-practices/subnets.md
@@ -177,6 +176,0 @@ If you deploy nodes in private subnets (IPv4 and IPv6), consider creating a NAT
-### Use Cloud9 to access Private Clusters
-
-AWS Cloud9 is a web-based IDE than can run securely in Private Subnets without ingress access, using AWS Systems Manager. Egress can also be disabled on the Cloud9 instance. [Learn more about using Cloud9 to access private clusters and subnets.](https://aws.amazon.com/blogs/security/isolating-network-access-to-your-aws-cloud9-environments/)
-
-![illustration of AWS Cloud9 console connecting to no-ingress EC2 instance.](/images/eks/latest/best-practices/images/networking/subnet_image-2.jpg)
-