AWS solutions documentation change
Summary
Updated VPC quota notes and added clarification about existing VPC deployments not creating new VPCs/endpoints
Security assessment
Changes are operational clarifications about resource consumption during deployment. No security vulnerabilities are addressed, and no security features are documented.
Diff
diff --git a/solutions/latest/spatial-data-management-on-aws/operations-planning.md b/solutions/latest/spatial-data-management-on-aws/operations-planning.md index 289861486..088617357 100644 --- a//solutions/latest/spatial-data-management-on-aws/operations-planning.md +++ b//solutions/latest/spatial-data-management-on-aws/operations-planning.md @@ -84 +84 @@ Before deploying this solution, verify the following quotas in your AWS account: - * VPCs per region: Default 5 (solution creates 1 VPC) + * VPCs per Region: Default 5 (the solution creates 1 VPC when not using an existing VPC) @@ -86 +86 @@ Before deploying this solution, verify the following quotas in your AWS account: - * VPC endpoints per VPC: Default 50 (solution creates 8 endpoints) + * VPC endpoints per VPC: Default 50 (the solution creates up to 14 endpoints when not using an existing VPC) @@ -90,0 +91,4 @@ Before deploying this solution, verify the following quotas in your AWS account: +###### Note + +If you deploy into an existing VPC using the `ExistingVpcId` parameter, the solution does not create a new VPC and does not consume a VPC quota slot. You must pre-create all required VPC endpoints before deploying — the solution validates that they exist but does not create them. + @@ -110 +114 @@ Integration Planning -Production Deployment Recommendations +Bring your own VPC