AWS cdk documentation change
Summary
Fixed markdown link syntax for CLI option and replaced specific permissions boundary name with a placeholder in example command
Security assessment
The changes are documentation formatting improvements and example standardization. The placeholder replacement prevents users from accidentally copying a literal boundary name, but this is a usability/clarity improvement rather than a security fix. No specific vulnerability or security incident is addressed.
Diff
diff --git a/cdk/v2/guide/customize-permissions-boundaries.md b/cdk/v2/guide/customize-permissions-boundaries.md index 19912a7e6..c5d82e6f2 100644 --- a//cdk/v2/guide/customize-permissions-boundaries.md +++ b//cdk/v2/guide/customize-permissions-boundaries.md @@ -31 +31 @@ After creating the permissions boundary, you can enforce it for the AWS CDK by a -Use the `[--custom-permissions-boundary](./ref-cli-cmd-bootstrap.html#ref-cli-cmd-bootstrap-options-custom-permissions-boundary)` option and specify the name of the permissions boundary to apply. The following is an example that applies a permissions boundary named `cdk-permissions-boundary`: +Use the [\--custom-permissions-boundary](./ref-cli-cmd-bootstrap.html#ref-cli-cmd-bootstrap-options-custom-permissions-boundary) option and specify the name of the permissions boundary to apply. The following is an example that applies a permissions boundary named `cdk-permissions-boundary`: @@ -34 +34 @@ Use the `[--custom-permissions-boundary](./ref-cli-cmd-bootstrap.html#ref-cli-cm - $ cdk bootstrap --custom-permissions-boundary cdk-permissions-boundary + $ cdk bootstrap --custom-permissions-boundary <cdk-permissions-boundary>