Hey, I have just migrated my api from digital ocean to AWS lambda. After doing all the necessary steps, I am getting CORS, error,

signin:1 
 Access to fetch at 'https://8fx6k5jmyg.execute-api.eu-central-1.amazonaws.com/auth/session/refresh' from origin 'https://loquacious-crostata-a45e75.netlify.app' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Hey @Ayush6543

Using the editor provided by AWS, create a new config file and write the following code:

Which page are you referring to?

If you are using express, you can continue to use express framework

I mean I am using express and have deployed my app to aws lambda, When I try to sign in it gives me the CORS error, and I am following the guide to setup.

The /dev should be in apiGatewayPath config and apiBasePath should be /auth

Is it ok to use

cors

instead of

@middy/http-cors @middy/core

Yea. If you are using express, then you should not use middy

Should I set

isInServerlessEnv: true,

when I am using express as a framework to deploy on AWS Lambda.

Yes you should

In setting up API Gateway, and cors, it is saying to setup manually in the AWS console. But I am using serverless package. Can't I specify this is in my

serverless.yaml

. If so How? This is my

serverless.yaml

# Welcome to Serverless!
#
# This file is the main config file for your service.
# It's very minimal at this point and uses default values.
# You can always add more config options for more control.
# We've included some commented out config examples here.
# Just uncomment any of them to get that config option.
#
# For full config options, check the docs:
#    docs.serverless.com
#
# Happy Coding!

service: serverless-chrome-extension-app
# app and org for use with dashboard.serverless.com
#app: your-app-name
#org: your-org-name

# You can pin your service to only deploy with a specific Serverless version
# Check out our docs for more details
frameworkVersion: "3"

provider:
  name: aws
  runtime: nodejs14.x
  stage: dev
  region: eu-central-1

# you can overwrite defaults here
#  stage: dev
#  region: us-east-1



functions:
  hello:
    handler: app.server
    events: # events trigger lambda functions
      - http: # this is an API Gateway HTTP event trigger
          path: /
          method: ANY
          cors: true
      - http: # all routes get proxied to the Express router
          path: /{proxy+}
          method: ANY
          cors: true

Which serverless package are you using?

"serverless-http": "^3.1.0", serverless: 3.25

You need to add /dev/auth in apiBasePath on the frontend

Thanks

Nice