serverless/serverless

For support requests please search or create posts on Serverless Forum: https://forum.serverless.com

Christopher R Hill

@aiur100

Hey everyone! Is there a newer local API Gateway + Lambda workflow that people have been using? I am still using the serverless-offline plugin, and various offline plugins like the one for DynamoDB. I get the feeling I am "behind the times" already. :) Any suggestions would be great.

Daniil

@reflash

hey! has anyone faced an issue when zipped package contains duplicate files (same name, same path)?

Wayne Durack

@Trolleymusic

Hello, I've got a question as I was about to file a bug report - but am wondering if it is a bug, or if there's an intention behind the change:

So serverless/serverless#9281

Includes the line

Remove handling of internal noDeploy option

And the release information for 2.36.0 includes the line:

Remove support for internal noDeploy option (serverless/serverless#9281) (serverless/serverless@688d09b) (Mariusz Nowak)

And ever since then, the --noDeploy cli flag does not work. I can't do a dry-run deployment.

This contradicts the documentation, but the documentation could be out of date.

Does anyone know what the intention was behind removing noDeploy and if there's a way of running a dry-run deploy from the command line?

1 reply

ok牧場

@okbokujo123_twitter

hello.
Can I run runtime python3.8 on serverless.ts?

  // import the function via paths
  functions: {
    hello,
    hello2: {
      handler: `handlers/hello2/test.lambda_handler`, // handlers/hello2/test.py
      runtime: 'python3.8',
    }
  },

Vlad Florin Sodringa

@vladoski

Hi guys, I'm trying to implement a very trivial Lambda Layer in AWS using Serverless but doesn't work.

I can see it in AWS but if I try to import it in my code, gives me an error saying that it can't find the Python module

my serverless.yml is this:

service: sapi-layers

frameworkVersion: ">=1.67.3"

provider:
  name: aws
  runtime: python3.8
  lambdaHashingVersion: 20201221
  region: eu-central-1

package:
  exclude:
    - node_modules/**
    - venv/**
    - .direnv/**

functions:
  esg:
    handler: esg.esg.handler
    events:
      - http:
          path: /esg/{proxy+}
          method: ANY
    layers:
      - { Ref: SharedLambdaLayer }

  risk:
    handler: risk.risk.handler
    events:
      - http:
          path: /risk/{proxy+}
          method: ANY
    layers:
      - { Ref: SharedLambdaLayer }

layers:
  shared:
    path: shared
    compatibleRuntimes:
      - python3.8
    allowedAccounts:
      - "*" # ALL accounts!

custom:
  pythonRequirements:
    usePoetry: true
    # dockerizePip: non-linux

plugins:
  - serverless-python-requirements

Raviteja Lingineni

@rlingineni

Hey All, I'm getting this error of spawn E2BIG when doing serverless deploy which is new for me. I think some part of the package is too large perhaps? I'm not exactly sure which part, or how to go about fixing this. It used to deploy just fine, I did a clean npm install, and that may also have caused the issue? I have the aws-sdk as a devDependency for local debugging, I'm not sure if that's also being packaged here.

2 replies

Jonathan Demirgian

@Quidge

Is it possible to provision an SNS topic without related it to a lambda? All examples I've seen that use lambdas create the SNS topic for use within a lambda. Can sls be used as a general purpose infra provisioning tool like this?

Pranav Malaviya

@pranavmalaviya2

Hi all,
I am creating a multi-service serverless architecture and facing some difficulties.

All the services contain at least 1 lambda and this lambda is triggered by an API endpoint.
I am following Shared API gateway from this guideline.
https://www.serverless.com/framework/docs/providers/aws/events/apigateway#share-api-gateway-and-api-resources

I can deploy 1st service with endpoint path "api/thingOne", but getting following error when I deploy the second lambda with the endpoint "api/thingTwo"

Error: ApiGatewayResourceApi - Another resource with the same parent already has this name: API

That was expected as per the guideline. "Cloudformation will throw an error if we try to generate an existing path resource."

To avoid that the document says "we reference the resource ID of /posts" and they added

restApiResources:
      posts: xxxxxxxxxx

My question is what is this 'xxxxxx'?

1 reply

Eliza D

@elizad

any advice, from where to start with serverless?

Stephen Rust

@probablyabear

Hi all - have a quick question about deployment. In my org, in order to deploy AWS resources, I have to assume a certain role, eg: aws-vault exec {some-org-role} ... Is there a way to configure this in serverless.yml or through serverless config credentials for this service I'm working on? FYI, I've already configured my default AWS profile via serverless config credentials

Morgan Litton

@TechTeam12

Hey everyone, not sure that this is a new question, but I'm getting a deprecation warning

Deprecation warning: Variables resolver reports following resolution errors:
              - Cannot resolve variable at "provider.deploymentBucket.name": Value not found at "opt" source

Any input for what is going on, or where I can start to understand this issue?

Morgan Litton

@TechTeam12

I tracked down a variablesResolutionMode field in the serverless documentation, but that causes issues for serverless-offline and the application errors with the above.

Aleksei Tcelishchev

@casualuser

Hello everyone!

Any gurus here with deep experience in splitting huge API?
I'm hitting here issue with Maximum policy size of 10240 bytes exceeded for role
And this happens already after serverless-plugin-split-stacks and
serverless-plugin-custom-roles applied and API split in smaller chunks.

After that cloudformation-template-update-stack.json still like 200Kb size.

Please suggest something or point with a proper direction for research.

Aleksei Tcelishchev

@casualuser

for all interested persons in reasons of Maximum policy size of 10240 bytes exceeded for role which not solvable with split-stacks
serverless/serverless#9517

Tim Stackhouse

@tstackhouse

Where does one find the 1.x docs? I can't find the docs repo on github anywhere, and there's no version toggle on the docs site

Domingo Tamayo

@dgptamayo

hi all. i'm trying to find any documentation/references about the 'custom' property in serverless.yml. can anybody point me in the right direction?

chimmy-changa

@chimmy-changa

Hi all,
I'm struggling with resolving relative imports in yaml files. How do I resolve path to a js file using relative path ?

This is my folder structure:

My serverless.yml file and the hello.yml file . I want to be able to point to the index.js file in the same directory as hello.yml file but unable to do it:

Gareth McCumskey

@garethmcc

@chimmy-changa handler: functions/index.handler

the format is path/to/file/filename.functioname

Greg Swallow

@gswallow

Hi all! I am brand new to serverless and I'm jumping in as a pretty dense "sysadmin" type. When I run serverless deploy... on a stack I just cloned, it creates an AWS::ApiGateway::Deployment resource whose name changes each time serverless deploy is run:

    ApiGatewayDeployment1622610163204: {
      "Type": "AWS::ApiGateway::Deployment",
      Properties: {
        RestApiId: {
          Ref: ApiGatewayRestApi
        },
        StageName: dev
      },
      DependsOn: [
        ApiGatewayMethodGraphqlOptions,
        ApiGatewayMethodGraphqlPost,
        ApiGatewayMethodGraphqlopenPost,
        ApiGatewayMethodHealthcheckGet
      ]
    }

Problem is I have an AWS::WAFv2::WebAclAssociation resource that's created with static cloudformation and it fails with a WAFNonexistentItemException error (https://docs.aws.amazon.com/waf/latest/APIReference/API_AssociateWebACL.html):

  WebAclToApiGateway:
    Type: AWS::WAFv2::WebACLAssociation
    Properties:
      ResourceArn: !Join
        - ""
        - - "arn:aws:apigateway:${opt:region, self:provider.region}::/restapis/"
          - !Ref ApiGatewayRestApi
          - "/stages/${self:provider.stage}"
      WebACLArn: !GetAtt WafWebACL.Arn

The stage doesn't exist until the AWS::ApiGateway::Deployment resource exists, so I assume I need to DependsOn that resource but its name changes. Is there a variable I should be looking for as part of a plugin that I can use?

Greg Swallow

@gswallow

I think the answer is ${sls:instanceId}

Ben Collier

@bencollier_twitter

Hi all - having an issue with deployment of a few of our lambdas. AWS is complaining that it can't find the relevant shared object files (.so) - we've tried turning off "slim" and also specifying the .so files in the DockerExtraFiles parameter, but none of these seem to work. Has anyone else experienced this, and is there anything obvious we may be doing wrong. These lambdas all work absolutely fine locally.

Aditya Agarwal

@aditya81070_twitter

Hello all, I am writing a lambda authoriser and want to use context.identity.sourceIp, method.request.headers.Authorization as identitySource. When I deploy the application to AWS, the authorizer is set up correctly and things are working fine.

But when I run my code locally (I am using serverless-offline), I get the error Serverless Offline only supports retrieving tokens from the headers (λ: my-auth). Here is the complete code:

functions:
  auth:
    handler: handlers/auth.auth
    vpc: ${self:custom.vpc}
  lambda-trigger:
    handler: handlers/lambda-trigger.lambdaTrigger
    timeout: 10
    events:
      - http:
          method: post
          path: /lambda-trigger
          cors: true
          authorizer:
            name: auth
            type: REQUEST
            identitySource: method.request.header.Authorization, context.identity.sourceIp
            resultTtlInSeconds: 0

Aleksei Tcelishchev

@casualuser

Hi all - having an issue with deployment of a few of our lambdas. AWS is complaining that it can't find the relevant shared object files (.so) - we've tried turning off "slim" and also specifying the .so files in the DockerExtraFiles parameter, but none of these seem to work. Has anyone else experienced this, and is there anything obvious we may be doing wrong. These lambdas all work absolutely fine locally.

if you're packing locally then you have to use same type of distro for docker image to build packages at as lambda env looks like so use f.e. public.ecr.aws/lambda/python:3.8 or ec2 instance with amazon linux
also using layers is highly recommended for this

mr. Romeijn

@mr-romeijn

Hello, I have a question regarding AWS Lambda event config. I've made a Lambda with an onSuccess handler which works fine when using the Event invocation type. I want to add a http api event but obviously this does not invoke the associated function with the Event invocation type. Is this possible to configure? Could not find anything regarding this in the docs

Trevor Marburger

@trevormarburger

Hello - the serverless docs mention that all GCP Cloud Function event types are supported, but I am only seeing HTTP & PubSub examples in the documentation. Has anyone successfully deployed a GCF with a Cloud Storage object.finalize trigger?

Trevor Marburger

@trevormarburger

@ambhojgoyal - did you ever find a solution to this? If so, what is it - I am running into the same limitation

What will be the event type for google cloud storage like pub/sub has :"providers/cloud.pubsub/eventTypes/topic.publish" ?

Ubani

@ubaniabalogun

Hi all, I'm developing a serverless plugin and my use-case requires me to automatically add resources to the serverless configuration BEFORE variable resolution happens. I used to accomplish this by adding those resources in the plugins constructor by modifying this.serverless.service.resources but this no longer works since serverless 2.46.0

Is there a more appropriate way to add auto-generated resources to serverless prior to variable resolution? Or alternatively is there a way to manually call variable resolution on an autogenerated resource?
I'm facing this challenge because my plugin auto-generates resources from static files in the repository that contain serverless variables, but aren't directly referenced in serverless.yaml

Gareth McCumskey

@garethmcc

@ubaniabalogun I would recommend asking the question as an issue in the GitHub project. That way the team and community who work on the framework can answer that and maybe make sure that the process you used to use is catered for in the new way of doing things

Muse Mekuria

@sumew

Hi folks, I'm looking for a way to clean up serverless resources via lambda... is it possible at all to call serverless remove or something that produces the same effect from a lambda?

Gareth McCumskey

@garethmcc

@sumew serverless remove does a few things but the biggest is to instruct CloudFormation to delete a stack. Perhaps look into the SDK documentation around the CloudFormation service to do that

Crystal R Williams

@CORT0619

Hi, any time I run "sls deploy -v" I'm receiving the error "Error: Profile ___ does not exist". I've already tried a few things like running serverless config credentials with the correct profile that I want to use but it's still telling me profile doesn't exist with a different profile.

Gareth McCumskey

@garethmcc

@CORT0619 Do you have a property called profile in your serverless.yml? The profile refers to an AWS connection profile stored in your ~/.aws/credentials file. If you do not have that file and you are referencing a profile in your serverless.yml you will see that message

Crystal R Williams

@CORT0619

Yes, i added that after looking online and it does reference a named profile in my credentials file.

Crystal R Williams

@CORT0619

@garethmcc do you know if it's possible to verify serverless is referencing the credentials file? i'm just at a loss because a few months ago I had no issue with this.

Gareth McCumskey

@garethmcc

If you have a profile property it is referencing the profile in that credentials file

Aditya Avanth

@AdityaAvanth_twitter

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

@aminshamim

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:
Path[0]:
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

lcranga

@lcranga

I am trying to use https://nestjs.com/ in AWS serverless. So can you send me a working example?

Lewis

@6ewis

I am not getting ssm value back on the lambda. Any idea? serverless/serverless#9676

VikramNisarga

@VikramNisarga

Hey People, I'm unable to find examples of Azure Java functions using serverless, is it supported?

Where communities thrive

People

Repo info

Activity