AWS verifiedpermissions documentation change
Summary
Changed 'AWS CloudFormation stack' to 'CloudFormation stack' for terminology consistency
Security assessment
The change is a non-substantive terminology update (removing redundant 'AWS' prefix). No security implications or documentation changes detected.
Diff
diff --git a/verifiedpermissions/latest/userguide/policy-stores-api-userpool-considerations-troubleshooting.md b/verifiedpermissions/latest/userguide/policy-stores-api-userpool-considerations-troubleshooting.md index 68afdec1b..f9ac8a0dc 100644 --- a//verifiedpermissions/latest/userguide/policy-stores-api-userpool-considerations-troubleshooting.md +++ b//verifiedpermissions/latest/userguide/policy-stores-api-userpool-considerations-troubleshooting.md @@ -56 +56 @@ For more information about Lambda function logs, see [Using Amazon CloudWatch Lo -After you complete setup of an API-linked policy store, you must attach the Lambda authorizer to your API. If you can't locate your authorizer in the API Gateway console, the additional resources for your policy store might have failed or not deployed yet. API-linked policy stores deploy these resources in an AWS CloudFormation stack. +After you complete setup of an API-linked policy store, you must attach the Lambda authorizer to your API. If you can't locate your authorizer in the API Gateway console, the additional resources for your policy store might have failed or not deployed yet. API-linked policy stores deploy these resources in an CloudFormation stack.