CORS Preflight fails on HTTP API Gateway

Hello,

The issue you're facing is likely due to the way AWS API Gateway handles CORS preflight requests. By default, API Gateway does not automatically handle CORS preflight requests for HTTP APIs.

If you don't have any stages defined in your HTTP API Gateway, and you're using the default stage, follow the below steps:

1.Create a new route for the OPTIONS method with the same path as your existing route (e.g., /{proxy+}). 2.For the new OPTIONS route, configure a mock integration to return the necessary CORS headers in the response:

{
  "statusCode": 200,
  "headers": {
    "Access-Control-Allow-Headers": "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token'",
    "Access-Control-Allow-Origin": "'*'",
    "Access-Control-Allow-Methods": "'OPTIONS,GET,PUT,POST,DELETE'"
  }
}

3. Configure the OPTIONS route to bypass the JWT Authorizer by setting the authorization type to "None".

After these steps, the CORS preflight requests should be handled correctly, and you should no longer receive the 403 Forbidden error.