Chrome CORB blocking APIGateway lambda request

I had similar issue. I suggest using POSTMAN for debugging it as it shows headers and allows you to tweak whatever is needed in your request.

In my case I had to re-deploy my API after adding the header. Attaching screenshot in case it might be of help to some users:

Integration response:

Method response:

Postman's headers response - working:

I just needed to persevere apparently. Just in case anyone ever runs into this:

Despite APIGateway CORS enablement, CORS authority is passed to the lambda function with Lambda proxy integration enabled. Although the initial URI request was accepted at the APIgateway, it ultimately failed due to lack of headers in the lambda response. Somehow This triggered CORB instead of CORS. I don't know why.

The answer is to ensure CORS is enabled in the APIgateway and that the lambda function response callback pattern contains a "Access-Control-Allow-Origin" header.