AWS verifiedpermissions documentation change
Summary
Changed 'AWS CloudFormation stack' to 'CloudFormation stack' for terminology consistency
Security assessment
Terminology update without altering security guidance. The existing security advice about privileged credentials remains unchanged.
Diff
diff --git a/verifiedpermissions/latest/userguide/policy-stores-api-userpool.md b/verifiedpermissions/latest/userguide/policy-stores-api-userpool.md index e52ec3379..69b79e5de 100644 --- a//verifiedpermissions/latest/userguide/policy-stores-api-userpool.md +++ b//verifiedpermissions/latest/userguide/policy-stores-api-userpool.md @@ -121 +121 @@ The Lambda function that Verified Permissions creates for your API authorizer is -To create an API-linked policy store, you must sign in a highly-privileged AWS principal to the Verified Permissions console. This user deploys an AWS CloudFormation stack that creates resources across several AWS services. This principal must have the permission to add and modify resources in Verified Permissions, IAM, Lambda, and API Gateway. As a best practice, don't share these credentials with other administrators in your organization. +To create an API-linked policy store, you must sign in a highly-privileged AWS principal to the Verified Permissions console. This user deploys an CloudFormation stack that creates resources across several AWS services. This principal must have the permission to add and modify resources in Verified Permissions, IAM, Lambda, and API Gateway. As a best practice, don't share these credentials with other administrators in your organization.