AWS wellarchitected documentation change

Service: wellarchitected · 2026-05-04 · Documentation low

File: wellarchitected/latest/saas-lens/amazon-eks-saas.md

Summary

Updated three diagram captions for EKS SaaS architecture to focus on VPC/subnet structure and tenant isolation mechanisms

Security assessment

Changes highlight tenant isolation features (pod security policies, IAM policies) which are security controls, but don't fix vulnerabilities

Diff

diff --git a/wellarchitected/latest/saas-lens/amazon-eks-saas.md b/wellarchitected/latest/saas-lens/amazon-eks-saas.md
index b3de7d92a..3b5d157ca 100644
--- a//wellarchitected/latest/saas-lens/amazon-eks-saas.md
+++ b//wellarchitected/latest/saas-lens/amazon-eks-saas.md
@@ -19 +19 @@ First, you’ll notice that we have the foundational elements that are part of a
-![Multi-tenant AWS architecture with VPC across 3 availability zones, showing public and private subnets.](/images/wellarchitected/latest/saas-lens/images/image5.png)
+![VPC with three Availability Zones containing public and private subnets with microservices.](/images/wellarchitected/latest/saas-lens/images/image5.png)
@@ -27 +27 @@ This architecture only represents the foundational elements of our SaaS environm
-![Multi-zone VPC architecture with public and private subnets, NAT gateways, and tenant namespaces for Order and Product.](/images/wellarchitected/latest/saas-lens/images/image6.png)
+![VPC with three availability zones, each containing public and private subnets with tenant namespaces.](/images/wellarchitected/latest/saas-lens/images/image6.png)
@@ -39 +39 @@ To enhance the isolation story of our Amazon EKS environment, we’ll need to in
-![Diagram showing tenant isolation in Amazon EKS with separate namespaces and security policies.](/images/wellarchitected/latest/saas-lens/images/image7.jpeg)
+![Multi-tenant namespace isolation with pod security policies, IAM policies, and separate database tables per tenant.](/images/wellarchitected/latest/saas-lens/images/image7.jpeg)