AWS Security ChangesHomeSearch

AWS vpc-lattice documentation change

Service: vpc-lattice · 2025-02-27 · Documentation low

File: vpc-lattice/latest/ug/resource-gateway.md

Summary

Reorganized content and added detailed considerations section for resource gateways

Security assessment

Similar to the VPC documentation change, this is an organizational update with operational considerations, but does not address security vulnerabilities or introduce new security features.

Diff

diff --git a/vpc-lattice/latest/ug/resource-gateway.md
index 7ffb739e1..5da4b0899 100644
--- a/vpc-lattice/latest/ug/resource-gateway.md
+++ b/vpc-lattice/latest/ug/resource-gateway.md
@@ -5 +5 @@
-Security groupsIP address types
+ConsiderationsSecurity groupsIP address types
@@ -9 +9 @@ Security groupsIP address types
-A _resource gateway_ is the point that receives traffic into the VPC where a resource resides. It spans multiple Availability Zones. For your resource to be accessible from all [Availability Zones](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/), you should create your resource gateways to span as many Availability Zones as possible. At least one Availability Zone of the VPC endpoint and the resource gateway have to overlap. A VPC can have a maximum of 100 resource gateways. For more information, see [Quotas for VPC Lattice](https://docs.aws.amazon.com/vpc-lattice/latest/ug/quotas.html).
+A _resource gateway_ is the point that receives traffic into the VPC where a resource resides. It spans multiple Availability Zones.
@@ -18,0 +19,2 @@ The following diagram shows how a client accesses a resource through the resourc
+  * Considerations
+
@@ -29,0 +32,15 @@ The following diagram shows how a client accesses a resource through the resourc
+## Considerations
+
+The following considerations apply to resource gateways:
+
+  * For your resource to be accessible from all [Availability Zones](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/), you should create your resource gateways to span as many Availability Zones as possible.
+
+  * At least one Availability Zone of the VPC endpoint and the resource gateway have to overlap.
+
+  * A VPC can have a maximum of 100 resource gateways. For more information, see [Quotas for VPC Lattice](https://docs.aws.amazon.com/vpc-lattice/latest/ug/quotas.html).
+
+  * You can't create a resource gateway in a shared subnet.
+
+
+
+