AWS solutions documentation change
Summary
Added new parameters for deploying into existing VPC infrastructure: ExistingVpcId, ExistingVpcCidrBlock, ExistingIsolatedSubnetIds, ExistingPrivateSubnetIds, and ExistingOpenSearchVpcEndpointId
Security assessment
Changes enable deployment into existing VPCs but don't address any security vulnerabilities or weaknesses. This is a networking flexibility feature without security implications.
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 da607b154..cacd99217 100644 --- a//solutions/latest/spatial-data-management-on-aws/deployment-steps.md +++ b//solutions/latest/spatial-data-management-on-aws/deployment-steps.md @@ -68,0 +69,5 @@ Parameter | Description | Default | Valid Values +`ExistingVpcId` | ID of an existing VPC to deploy into instead of creating a new one. When provided, the solution skips VPC creation and deploys into your existing VPC. See [Reuse existing networking infrastructure](./reuse-existing-networking.html) for prerequisites. | Empty | Valid VPC ID (`vpc-<hex>`) or empty +`ExistingVpcCidrBlock` | CIDR block of the existing VPC (for example, `10.0.0.0/16`). Required when `ExistingVpcId` is set. | Empty | Valid CIDR range or empty +`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 +`ExistingOpenSearchVpcEndpointId` | ID of the Amazon OpenSearch Serverless VPC endpoint in the existing VPC. Required when `ExistingVpcId` is set. | Empty | Valid VPC endpoint ID (`vpce-<hex>`) or empty