AWS solutions documentation change
Summary
Added guidance on changing the solution's default CIDR using CloudFormation templates
Security assessment
The change describes configuration steps for CIDR adjustments but does not directly address security issues or document security features.
Diff
diff --git a/solutions/latest/centralized-logging-with-opensearch/frequently-asked-questions.md b/solutions/latest/centralized-logging-with-opensearch/frequently-asked-questions.md index fafcaad3d..dbd867691 100644 --- a//solutions/latest/centralized-logging-with-opensearch/frequently-asked-questions.md +++ b//solutions/latest/centralized-logging-with-opensearch/frequently-asked-questions.md @@ -87,0 +88,6 @@ Yes. You can either launch the solution with a new VPC or launch the solution wi +**Q: How can I change the default CIDR of the solution?** + +To change the default CIDR of the solution, you must first create a custom CIDR VPC and then deploy CLO using the 'Existing VPC' template. + +You may use the following AWS CloudFormation templates to do so. First, deploy this [CloudFormation template](https://github.com/aws-solutions/centralized-logging-with-opensearch/files/13974602/3-layer-subnets.template.json) and when prompted, enter the CIDR prefix you want for your VPC. After the CloudFormation stack has finished deploying, continue with the deployment of the CLO solution using the [Launch with an existing VPC](https://docs.aws.amazon.com/solutions/latest/centralized-logging-with-opensearch/launch-with-amazon-cognito-user-pool.html#step-1.-launch-the-stack) option. +