AWS cognito documentation change
Summary
Updated references to AWS services by removing redundant 'AWS' prefix from CloudFormation and AWS CLI mentions
Security assessment
The change is a stylistic update to service naming conventions without altering security implications of cross-account Lambda triggers documentation. No security vulnerabilities or configuration changes are addressed.
Diff
diff --git a/cognito/latest/developerguide/cognito-user-pools-working-with-lambda-triggers.md b/cognito/latest/developerguide/cognito-user-pools-working-with-lambda-triggers.md index b920e6731..2112d41ad 100644 --- a//cognito/latest/developerguide/cognito-user-pools-working-with-lambda-triggers.md +++ b//cognito/latest/developerguide/cognito-user-pools-working-with-lambda-triggers.md @@ -91 +91 @@ Managed login returns errors that Lambda triggers generate as error text above t - * You can add a Lambda function in another AWS account as a trigger for your user pool. You must add cross-account triggers with the [CreateUserPool](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_CreateUserPool.html) and [UpdateUserPool]() API operations, or their equivalents in AWS CloudFormation and the AWS CLI. You can't add cross-account functions in the AWS Management Console. + * You can add a Lambda function in another AWS account as a trigger for your user pool. You must add cross-account triggers with the [CreateUserPool](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_CreateUserPool.html) and [UpdateUserPool]() API operations, or their equivalents in CloudFormation and the AWS CLI. You can't add cross-account functions in the AWS Management Console.