AWS apigateway documentation change
Summary
Updated documentation to use 'CloudFormation' instead of 'AWS CloudFormation' in Lambda integration permissions section
Security assessment
The change is a minor terminology update without altering security implications. It maintains existing guidance about required permissions for Lambda invocations when using CLI/CloudFormation/SDK, but doesn't address any specific vulnerability or add new security content.
Diff
diff --git a/apigateway/latest/developerguide/http-api-troubleshooting-lambda.md b/apigateway/latest/developerguide/http-api-troubleshooting-lambda.md index 769129d17..f2092881c 100644 --- a//apigateway/latest/developerguide/http-api-troubleshooting-lambda.md +++ b//apigateway/latest/developerguide/http-api-troubleshooting-lambda.md @@ -84 +84 @@ In this case, the logs show that API Gateway didn't have the required permission -When you create a Lambda integration in the API Gateway console, API Gateway automatically configures permissions to invoke the Lambda function. When you create a Lambda integration by using the AWS CLI, AWS CloudFormation, or an SDK, you must grant permissions for API Gateway to invoke the function. The following [add-permission](https://docs.aws.amazon.com/cli/latest/reference/lambda/add-permission.html) commands grant permission for different HTTP API routes to invoke a Lambda function. +When you create a Lambda integration in the API Gateway console, API Gateway automatically configures permissions to invoke the Lambda function. When you create a Lambda integration by using the AWS CLI, CloudFormation, or an SDK, you must grant permissions for API Gateway to invoke the function. The following [add-permission](https://docs.aws.amazon.com/cli/latest/reference/lambda/add-permission.html) commands grant permission for different HTTP API routes to invoke a Lambda function.