This plugin provides a temporal solution to the issue described here.
- Inside your project's serverless.ymlfile, add the following entry in thepluginssection.
plugins:
  - serverless-offline
  - serverless-offline-lambda-function-urls- Configure the port where the new server will be running. By default, the server will run on 3003.
serverless-offline:
  urlLambdaFunctionsHttpPort: 3003
  # Optional - choose which HTTP verb(s) to enable. If omitted, GET and POST will be enabled
  urlLambdaFunctionsHttpVerbs:
    - GET
    - DELETE- Configure a lambda url function. When you add the urloption, the handler will expose it as an HTTP endpoint(/dev/ping) with the verbs specified inurlLambdaFunctionsHttpVerbsorGETandPOSTif that setting is not specified. The HTTP endpoint doesn't go through the API Gateway, which means that you can set your owntimeoutand it will respect it. Traditionally, the API Gateway would timeout after 30 seconds.
ping:
  handler: ./src/functions/ping.handler
  url: true
  timeout: 120 # The handler will timeout after 2 minutes and API Gateway won't interrupt it- Run serverless offlineand the plugin will be triggerred by theoffline:start:initevent.
serverless offline start