AWS solutions documentation change
Summary
Updated subnet configuration documentation: clarified optional use of isolated subnets and specified private subnets require outbound internet access.
Security assessment
Changes clarify network configuration options without addressing security vulnerabilities or introducing new security features. Modifications are operational improvements to deployment documentation.
Diff
diff --git a/solutions/latest/spatial-data-management-on-aws/deployment-steps.md b/solutions/latest/spatial-data-management-on-aws/deployment-steps.md index cacd99217..239e6991c 100644 --- a//solutions/latest/spatial-data-management-on-aws/deployment-steps.md +++ b//solutions/latest/spatial-data-management-on-aws/deployment-steps.md @@ -71,2 +71,2 @@ Parameter | Description | Default | Valid Values -`ExistingIsolatedSubnetIds` | Comma-separated IDs of isolated subnets (no internet route) in the existing VPC. Required when `ExistingVpcId` is set. | Empty | Comma-separated subnet IDs or empty -`ExistingPrivateSubnetIds` | Comma-separated IDs of private subnets (NAT gateway route) in the existing VPC. Required when `ExistingVpcId` is set. | Empty | Comma-separated subnet IDs or empty +`ExistingIsolatedSubnetIds` | Comma-separated IDs of isolated subnets (no internet route) in the existing VPC. Optional — if omitted, all Lambdas are placed in private subnets. | Empty | Comma-separated subnet IDs or empty +`ExistingPrivateSubnetIds` | Comma-separated IDs of private subnets (with outbound internet route) in the existing VPC. Required when `ExistingVpcId` is set. | Empty | Comma-separated subnet IDs or empty