AWS Lambda advanced configuration

Application Security reports security events and includes details associated with the offending request's origin. Some of the protection features, such as Remote Command Execution, SQL Injection and Illegal File Access, provide protection regardless of the AWS Lambda trigger point and event type. For some other protection features such as Malicious File Upload and Malicious Payload, the HTTP Event is required. If the API Gateway is the trigger point, the Lambda Proxy Integration configuration must be configured in AWS:

1. In your AWS account, go to API Gateway and select the API Gateway that's linked to your function.
2. In the GET tab, select Integration Request in the top-right corner.
3. Select Use Lambda Proxy Integration. This setting must be selected for the API Gateway in order for the Application Security layer to access the request's details in the Lambda events.