Request body is empty when calling lambda endpoint in API Manager 4.3.0 version

[niranRameshPeiris]

Description

Hi team,

We have noticed that WSO2 does not pass the request body to the lambdas in the API Manager 4.3.0 version. However, in 4.2, the request body passes to the lambdas perfectly. The steps we have followed in both 4.2 and 4.3 are as below.

1. Download both API Manager 4.2/4.3 pack.
2. Update to the latest.
3. Create and Publish an AWS Lambda API.
4. Subscribe to an Application.
5. Invoke both the APIs with a payload.

curl --location 'https://localhost:8243/testLambda/1.0.0' \
--header 'accept: */*' \
--header 'Authorization: Bearer eyJ4NXQiOiJPREUzWTJa....2YhNBNFeZl6IAwN8OryQ' \
--header 'Content-Type: application/json' \
--data '{
    "name": "niran"
}'

We enabled debug logs to the org.wso2.carbon.apimgt.gateway.mediators.AWSLambdaMediator class before invoking this API. While analyzing the logs we were able to identify that the body is not sending in 4.3, but in 4.2 we can see the body.

API Manager-4.2.0
"body":{"name":"niran"}

API Manager-4.3.0
"body":{}

Thanks & Regards,
Niran Peiris

Steps to Reproduce

1. Download both API Manager 4.2/4.3 pack.
2. Update to the latest.
3. Create and Publish an AWS Lambda API.
4. Subscribe to an Application.
5. Invoke both the APIs with a payload.

curl --location 'https://localhost:8243/testLambda/1.0.0' \
--header 'accept: */*' \
--header 'Authorization: Bearer eyJ4NXQiOiJPREUzWTJa....2YhNBNFeZl6IAwN8OryQ' \
--header 'Content-Type: application/json' \
--data '{
    "name": "niran"
}'

Affected Component

APIM

Version

4.3.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response