AWS solutions documentation change
Summary
Updated punctuation formatting (apostrophes and dashes) in troubleshooting content and VPC limit documentation
Security assessment
Changes involve typographical corrections (straight quotes to curly quotes, en-dash to hyphen) without modifying security-related content. The mention of AdministratorAccess policy was pre-existing and not part of the actual changes.
Diff
diff --git a/solutions/latest/generative-ai-application-builder-on-aws/troubleshooting.md index 506096192..b4704da3d 100644 --- a/solutions/latest/generative-ai-application-builder-on-aws/troubleshooting.md +++ b/solutions/latest/generative-ai-application-builder-on-aws/troubleshooting.md @@ -5 +5 @@ -Problem: Deploying a VPC-enabled configuration, with Create a VPC for me, failsProblem: Use case stack can't be deleted in CloudFormation after the Deployment dashboard stack gets deletedProblem: Use case UI does not reflect changes in settings +Problem: Deploying a VPC-enabled configuration, with Create a VPC for me, failsProblem: Use case stack can’t be deleted in CloudFormation after the Deployment dashboard stack gets deletedProblem: Use case UI does not reflect changes in settings @@ -27 +27 @@ Some limits to be aware of (per account, per Region): - * Number of VPCs – 5 + * Number of VPCs - 5 @@ -29 +29 @@ Some limits to be aware of (per account, per Region): - * Number of public IP addresses – 5 + * Number of public IP addresses - 5 @@ -31 +31 @@ Some limits to be aware of (per account, per Region): - * Number of Gateway VPC Endpoints – 20 + * Number of Gateway VPC Endpoints - 20 @@ -38 +38 @@ Some limits to be aware of (per account, per Region): -## Problem: Use case stack can't be deleted in CloudFormation after the Deployment dashboard stack gets deleted +## Problem: Use case stack can’t be deleted in CloudFormation after the Deployment dashboard stack gets deleted @@ -60 +60 @@ Recreate the deleted IAM role to enable the deletion of the CloudFormation stack - 2. Add the necessary permissions. If you're unsure about the required permissions, you can use the AWS managed **AdministratorAccess** policy. + 2. Add the necessary permissions. If you’re unsure about the required permissions, you can use the AWS managed **AdministratorAccess** policy.