AWS verifiedpermissions documentation change
Summary
Updated AWS CDK acronym expansion in documentation
Security assessment
Change only expands the CDK acronym to 'AWS CDK' for clarity, with no security implications.
Diff
diff --git a/verifiedpermissions/latest/userguide/policy-stores-api-userpool.md b/verifiedpermissions/latest/userguide/policy-stores-api-userpool.md index 222759663..e52ec3379 100644 --- a//verifiedpermissions/latest/userguide/policy-stores-api-userpool.md +++ b//verifiedpermissions/latest/userguide/policy-stores-api-userpool.md @@ -38 +38 @@ To see an demo, see [Amazon Verified Permissions - Quick Start Overview and Demo -Policy stores that you create with the **Set up with API Gateway and an identity source** option in the Verified Permissions console aren’t intended for immediate deployment to production. With your initial policy store, finalize your authorization model and export the policy store resources to CloudFormation. Deploy Verified Permissions to production programmatically with the [AWS Cloud Development Kit (CDK)](https://aws.amazon.com/cdk). For more information, see [Moving to production with AWS CloudFormation](./policy-stores-api-userpool-considerations-production.html). +Policy stores that you create with the **Set up with API Gateway and an identity source** option in the Verified Permissions console aren’t intended for immediate deployment to production. With your initial policy store, finalize your authorization model and export the policy store resources to CloudFormation. Deploy Verified Permissions to production programmatically with the [AWS Cloud Development Kit (AWS CDK)](https://aws.amazon.com/cdk). For more information, see [Moving to production with AWS CloudFormation](./policy-stores-api-userpool-considerations-production.html).