Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • Jan 16 2019 18:39

    carlosandrebp on master

    upload email icon (compare)

  • Jan 15 2019 14:03

    carlosandrebp on master

    Icons update (compare)

  • Nov 13 2018 16:54
    hassankhan commented #3
  • Nov 02 2018 15:10
    hassankhan commented #3
  • Nov 02 2018 15:10
    hassankhan commented #3
  • Nov 01 2018 23:19
    hassankhan commented #3
  • Oct 29 2018 16:32
    hassankhan commented #3
  • Oct 24 2018 14:38
    hassankhan opened #3
  • Aug 14 2018 23:50

    carlosandrebp on master

    updates animations (compare)

  • Jul 19 2018 16:34
    brianneisler closed #1
  • Jul 19 2018 16:34
    brianneisler commented #1
  • Jul 18 2018 16:36

    andrepiresbp on master

    Updates (compare)

  • Jul 18 2018 15:50

    andrepiresbp on master

    Update (compare)

  • Jul 09 2018 19:25
    gornostal commented #59
  • Jul 09 2018 19:12
    maheshmasale commented #59
  • May 24 2018 23:39
    DavidWells removed as member
  • Feb 13 2018 19:40
    ivan-myob commented #54
  • Feb 08 2018 08:48
    julien2x opened #62
  • Dec 22 2017 16:14
    awcheng opened #61
  • Oct 23 2017 19:12
    dluu2015 closed #60
Aditya Avanth
Hi All,
I'm trying to enable cors on an AWS apigateway which is using lambda-proxy integration. The documentation says we can pass multiple origins to cors configuration (https://www.serverless.com/framework/docs/providers/aws/events/apigateway/#enabling-cors) , but when I check the integration response for OPTIONS method, The "Access-control-allow-origin" is only showing 1 origin. So, the api is failing when I'm firing the request from another origin. How to fix this? Any solutions Please?
Md. Aminul Islam Sarker

I am getting the following error. Is there any idea about it? Anyone?

cmdlet Select-String at command pipeline position 1
Supply values for the following parameters:
Select-String : Cannot bind argument to parameter 'Path' because it is an empty array.
At line:1 char:1

  • sls deploy
  • ~~
    • CategoryInfo : InvalidData: (:) [Select-String], ParameterBindingValidationException
    • FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyArrayNotAllowed,Microsoft.PowerShell.Commands.SelectStringCommand
I was running sls deploy command
I am trying to use https://nestjs.com/ in AWS serverless. So can you send me a working example?
I am not getting ssm value back on the lambda. Any idea? serverless/serverless#9676
Hey People, I'm unable to find examples of Azure Java functions using serverless, is it supported?
Diego Rainero
Hi all.
I can't find no documentation about timestream and serverless
is there some way to manage timestream? is it supported?
Daniel Craig
How can I upload a file to an s3 bucket at time of deploy?
Hello all,
node_modules aren't getting generated when i use serverless package any ideas?

Hello Everyone,

I have recently come across container support for lambda. To my knowledge, I know that serverless framework packages/zips the code and uploads to aws. Does anyone know if serverless framework supports this container workflow ?

By container workflow I mean: When we do serverless deploy:

  • Builds docker images corresponding to the lambda functions
    • Upload to ECR
    • Create or update lambda function to use the newly uploaded container image.

Thanks in advance.

what is the maximum timeout for serverless?
i put timeout: 60 but the gateway maximum seems to be 30?
@6ewis , I believe various resources have various timeouts. functions have 15, gateway has 30.
Does anyone know the implications on cost -- with a timeout of 60s?
  name: aws
  runtime: nodejs14.x
  stage: prod
  region: us-east-1
  timeout: 60
    lambda: true

Unable to find the reference to layer in resource section, especially when we enable the provisionedConcurrency or functionVersion set to true.

if we remove both provisionedConcurrency or functionVersion in serverless script, same code is working fine without any issues

  name: rtn
  name: aws
  region: us-west-2
  stackName: rtn-sls
    name: ${self:custom.S3BucketName.${opt:stage}}
    maxPreviousDeploymentArtifacts: 10
  deploymentPrefix: rtn/deployment
  runtime: nodejs12.x
  memorySize: 256
  timeout: 300

  # Lambda Configuration
  versionFunctions: false # Lambda Versioning

  # X-Ray Configuration
    lambda: true

  params: ${file(./env/${opt:stage}/parameters.json)}
  version: ${self:custom.params.Version}
  LayerVersion: ${self:custom.params.LayerVersion}
  s3Key: "https://s3.amazonaws.com/${self:custom.S3BucketName.${opt:stage}}/rtn-business-service/${self:custom.version}"

    devint: rtn-devint
    prod: rtn

  individually: true

    name: "rtn-api-router"
    handler: rtn-api-router.handler
      - !Ref rtnLayer
      artifact: "${self:custom.s3Key}/rtn-api-router-v${self:custom.version}.zip"
    provisionedConcurrency: 1

  - Resources:
        Type: AWS::Lambda::LayerVersion
            - nodejs12.x
            S3Bucket: ${self:custom.S3BucketName.${opt:stage}}
            S3Key: common-nodejs-lambda-layer/common-nodejs-lib-v${self:custom.LayerVersion}.zip
          LayerName: rtn-layer

Getting below error

Serverless Error ----------------------------------------

  ServerlessError: Could not find reference to layer: rtnLayer. Ensure that you are referencing layer defined in your service.
      at /Users/naveen/rtn-api-router/node_modules/serverless/lib/plugins/aws/package/compile/functions.js:739:15
      at Array.forEach (<anonymous>)
      at extractLayerConfigurationsFromFunction (/Users/naveen/rtn-api-router/node_modules/serverless/lib/plugins/aws/package/compile/functions.js:735:29)
      at AwsCompileFunctions.compileFunction (/Users/naveen/rtn-api-router/node_modules/serverless/lib/plugins/aws/package/compile/functions.js:458:9)
      at /Users/naveen/rtn-api-router/node_modules/serverless/lib/plugins/aws/package/compile/functions.js:680:64
      at Array.map (<anonymous>)
      at AwsCompileFunctions.compileFunctions (/Users/naveen/rtn-api-router/node_modules/serverless/lib/plugins/aws/package/compile/functions.js:680:37)
      at AwsCompileFunctions.tryCatcher (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/promise.js:547:31)
      at Promise._settlePromise (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/promise.js:729:18)
      at _drainQueueStep (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/async.js:93:12)
      at _drainQueue (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/async.js:86:9)
      at Async._drainQueues (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/async.js:102:5)
      at Immediate.Async.drainQueues (/Users/naveen/rtn-api-router/node_modules/bluebird/js/release/async.js:15:14)
      at processImmediate (internal/timers.js:456:21)

Hi all. Any serverless experts out there open to some contract work?
My startup is requiring a 3 months+ contract laying down some initial architecture and implemention in node. Fully serverless stack on AWS.
Details here:

Pm for more details
Many thanks

Akshay Kumar
Hi! I am trying to setup a few lambda functions with integration:lambda. When I do this, whatever I return from lambda gets returned as body.
Before using the integration:lambda in serverless.yml, I was using mitty to take care of cors. Does this mean that I have to pass cors related configuration in serverless.yml instead?
I have something like return { statusCode: 200, body: JSON.stringify("") } in the handler. When I inspect the response I get { statusCode: 200, body: "" } as the body of the response for the request.
I tried to go through the docs related to API Gateway Events. but I was not able to figure out how to setup functions using path and query parameters. So I switched to integration: lambda, as in this case the path and query parameters are probably automatically parsed as object and return as properties of event. But this messed up the response returned by the handlers.
Akshay Kumar
Can someone point me to a sample with integration:lambda showing the serverless.yml and the handler code?
Akshay Kumar
Hi all, i am new to serverless with azure and not able to find any docs for armTemplate use method in serverless.yaml
Can someone point me to any documentation they know about?
Hi, is there anyway we can change lambda provisionedConcurrency based on cron schedule. Like AWS::ApplicationAutoScaling::ScalableTarget in SAM
Greg Swallow
I wrote a cloudformation template. Serverless insists on reading the contents of a multi-line string and pullling variables out of it.
Greg Swallow
seriously is there no concept of a here document in serverless?
Greg Swallow
Is this thing dead?
Gareth McCumskey
@gswallow Could you clarify what you mean by a here document?
And can you clarigy why you would write a CloudFormation template? Serverless Framework provides you abstractions to reduce the amount of CF you need to write and then you do it directly in the serverless.yml in order to keep things together. Perhaps a little more of a description as to what it is you are trying to accomplish might help others advise on a good course of action

Getting "EventBridge rule <rule_name> already exists" error on redeployment
I am using native CF by setting useCloudFormation: true

    handler: index.receiveEvent
      - eventBridge:
          eventBus: <ARN of the event bus>
          - server.name
          - EVENT_NAME

Any help or guidance is much appreciated. Ty

Gareth McCumskey
@13colours Can you share the ouptut of serverless --version
Framework Core: 2.53.1
Plugin: 5.4.3
SDK: 4.2.6
Components: 3.14.2
Jeremy Corson
Good morning. Im exploring websockets for the first time this morning using the serverless framework. looks like i got it set up and i can test using websocket king and see my logs so im pretty excited about that. Im curious how people are woprking with them in a development setting becuase it seems there is no support for cors? So if my browser based react client attempts to use it it will just error
Jake Scott
Hi team, wondering when the next release is scheduled? Have a PR that we are excited to get our hands on :) serverless/serverless#9865
Gareth McCumskey
@jakejscott The best bet is to tell the team that in GitHub :)
Jake Scott
Cool thanks @garethmcc
Miguel Carvajal
does anyone has used 'serverless' as a library instead of a CLI app?
Hey. Does any know of good serverless-nodejs-typescript starter production project (Even javascript will be okay) ?
I am looking for production best practices examples like below
  1. middleware
  2. security
  3. how to add multiple microservices under one api gateway etc..
Hi, I need some help please :)
All of the sudden, sls deploy to dev is failing and we can't understand why.

The error is:

An error occurred: HttpApiStage - Cannot enable logging. Policy document length breaking Cloudwatch Logs Constraints, either < 1 or > 5120 (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: b47af8e7-47d7-4921-baf8-87de0f8ba253; Proxy: null).

Does anyone has any idea???
Thanks in advance!!!
Gareth McCumskey
@tomerdomshlak Do you make use of the nested stacks plugins of some kind?
The issue is around the fact that each deployed CloudFormation stack has to generate a IAM policy documents for various reasons. There is a limit as to how large any of these policy documents can be. If you werent using a nested stack plugin, usually you would have gotten an error about attempting to deploy more resources than allowed for a specific CloudFormation stack but using a nested stack plugin bypasses that so now your stack gets large enough to reach the limit of character size for an IAM policy
Hi @garethmcc . I'll start by saying big thank you for your quick response.
I'll consult with my team and send a response back.