AWS apigateway documentation change
Summary
Updated 'AWS CloudFormation' to 'CloudFormation' in Lambda authorizer configuration instructions
Security assessment
Branding update without altering the security implications of Lambda authorizer configuration requirements. The requirement to specify payload format versions remains unchanged.
Diff
diff --git a/apigateway/latest/developerguide/http-api-lambda-authorizer.md b/apigateway/latest/developerguide/http-api-lambda-authorizer.md index 1c5ae31a1..4411cfb35 100644 --- a//apigateway/latest/developerguide/http-api-lambda-authorizer.md +++ b//apigateway/latest/developerguide/http-api-lambda-authorizer.md @@ -13 +13 @@ You use a Lambda authorizer to use a Lambda function to control access to your H -The authorizer payload format version specifies the format of the data that API Gateway sends to a Lambda authorizer, and how API Gateway interprets the response from Lambda. If you don't specify a payload format version, the AWS Management Console uses the latest version by default. If you create a Lambda authorizer by using the AWS CLI, AWS CloudFormation, or an SDK, you must specify an `authorizerPayloadFormatVersion`. The supported values are `1.0` and `2.0`. +The authorizer payload format version specifies the format of the data that API Gateway sends to a Lambda authorizer, and how API Gateway interprets the response from Lambda. If you don't specify a payload format version, the AWS Management Console uses the latest version by default. If you create a Lambda authorizer by using the AWS CLI, CloudFormation, or an SDK, you must specify an `authorizerPayloadFormatVersion`. The supported values are `1.0` and `2.0`.