Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 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
Andrew Farrell
@amfarrell
Is there a way to run serverless deploy from a machine which does not have docker installed?
Gareth McCumskey
@garethmcc
Serverless by default does not use docker
justonequestion
@justonequestion:matrix.org
[m]
Hi, I have a function and while trying to use sls deploy it times out after 120000 ms
The package is not huge I think;
Serverless: Uploading function: translate (46 MB)...
prashant
@iprashant_twitter
Your Environment Information ---------------------------
Operating System: linux
Node Version: 11.2.0
Framework Version: 2.72.3 (local)
Plugin Version: 5.5.4
SDK Version: 4.3.2
Components Version: 3.18.2
TypeError [ERR_INVALID_ARG_TYPE]: The "original" argument must be of type Function. Received type undefined
at promisify (internal/util.js:257:11)
Getting above error
Puneet Kathar
@puneetkathar1
I made the latest PR #11347, can a maintainer kindly review it?
Chintan Shah
@chintanshahts

How can i enable the Encryption in AWS SQS

Encryption key type : Amazon SQS key (SSE-SQS)

Kevin Liang
@llkevin13579
@amfarrell Al’s deploy doesn’t need docker
txxnano
@Warkanlock
Hello everyone! I'm receiving a connection pool error on Lambdas and I think I know why, did anyone here destroy the connection after the callback?
Jeevan M D
@jmd9019
Hi everyone!.. Does this library supports DO functions? If yes can you send me guide
Lorenzo Andraghetti
@andraghetti
Hello! I would like to create an s3 inventory with serverless and read it from a lambda. How can I do that?
hik
@hik:aboveaverage.space
[m]
Hello, I am trying to implement:
https://www.serverless.com/blog/container-support-for-lambda but I am having issues, particularly with "path" must be string or buffer
Serverless.yml incoming in a moment
hik
@hik:aboveaverage.space
[m]
service: sumo-admin

frameworkVersion: '3'

custom:
  tableName: 'users-table-${self:provider.stage}'
  sumoTableName: 'sumo-table-${self:provider.stage}'
  wsgi:
    app: app.app

provider:
  name: aws
  runtime: python3.8
  stage: dev
  region: us-west-2
  ecr:
    images:
      app:
        path: ./
  iam:
    role:
      statements:
        - Effect: Allow
          Action:
            - dynamodb:Query
            - dynamodb:Scan
            - dynamodb:GetItem
            - dynamodb:PutItem
            - dynamodb:UpdateItem
            - dynamodb:DeleteItem
          Resource:
            - Fn::GetAtt: [ UsersTable, Arn ]
        - Effect: Allow
          Action:
            - ssm:*
          Resource:
            - "*"
  environment:
    USERS_TABLE: ${self:custom.tableName}
    SUMO_TABLE: ${self:custom.sumoTableName}

functions:
  api:
    image:
      name: app
    handler: wsgi_handler.handler
    events:
      - httpApi: '*'
    environment:
      SUMO_ACCESS_ID: ${ssm:/sumologic/sumoservice.access.key.id}
      SUMO_ACCESS_KEY: ${ssm:/sumologic/sumoservice.access.key.secret}
plugins:
  - serverless-wsgi
  - serverless-python-requirements
  - serverless-dotenv-plugin

resources:
  Resources:
    UsersTable:
      Type: AWS::DynamoDB::Table
      Properties:
        AttributeDefinitions:
          - AttributeName: userId
            AttributeType: S
        KeySchema:
          - AttributeName: userId
            KeyType: HASH
        ProvisionedThroughput:
          ReadCapacityUnits: 1
          WriteCapacityUnits: 1
        TableName: ${self:custom.tableName}
    SumoTable:
      Type: AWS::DynamoDB::Table
      Properties:
        AttributeDefinitions:
          - AttributeName: service_name
            AttributeType: S
        KeySchema:
          - AttributeName: service_name
            KeyType: HASH
        ProvisionedThroughput:
          ReadCapacityUnits: 1
          WriteCapacityUnits: 1
        TableName: ${self:custom.sumoTableName}
I'm not sure why "path" is undefined anywhere
hik
@hik:aboveaverage.space
[m]
Has anyone gotten serverless-wsgi and serverless-python-requirements to play nice for dockerizing a build?
I have the flags in the tutorial for doing this, but serverless just wants to package the wsgi handler normally without any references to docker
Thiago Cardoso
@thiagocardoso1988
hi everybody, does anybody has a reference to how create a subscription to SNS from a SQS using typescript`s serverless schema?
dreaminpast123
@minshi123
Has anyone else had a similar experience? When running a long-running application, especially with large call counts; compared with EC2/Fargate etc, Lambda is very expensive...
When should I choose Lambda/FaaS?(sometimes I feel like it's ok, but it's expensive...)
Guru
@GuruBrahmaraju
image.png
I am trying to fix this error
can any one help me
hik
@hik:aboveaverage.space
[m]
It's saying that the function you're targeting with that aws lambda permission doesn't exist.
"Why doesn't it exist" could be a bunch of reasons
Sometimes this can get weird if you have lambdas in other stacks that you're applying permissions to, aren't naming them correctly ("correctly" here means "that they match up to other places they're referenced"), maybe you have an issue where you should put DependsOn: GetAtt! [ "lambda", "arn" ] to make sure that CFN waits for the lambda to establish the permission
Walter
@McCo0L
Hey, I'm trying to deploy a nextjs application using serverless, something I did before for other environment, but now it's not working with the following error:
  DEBUG ─ Updating CloudFront distribution of ID XXXXXXXXX.

  error:
  Error [UriParameterError]: Expected uri parameter to have length >= 1, but found "" for params.Bucket
the deployment is over an existing Cloudfront distribution, trying to update with the following serverless.yml
name: FE

nextApp:
  component: "@sls-next/serverless-component@3.7.0"
  inputs:
    build:
      env:
        BASE_FE_URL: "https://stage.xxxxxxxxxxxxxx.com"
    memory: 1024
    bucketName: "XXXXXXXXXXXXX-XXXXXXXXXXX-app"
    bucketRegion: "us-west-2"
    cloudfront:
      distributionId: XXXXXXXXXX
      aliases: ["stage.xxxxxxxxxxxxxx.com"]
      defaults:
        forward:
          cookies: ["Auth"]
          headers: ["Authorization"]
      _next/data/*:
        forward:
          cookies: ["Auth"]
          headers: ["Authorization"]
      _next/image*:
        forward:
          cookies: ["Auth"]
          headers: ["Authorization"]
      _next/static/*:
        forward:
          cookies: ["Auth"]
          headers: ["Authorization"]
      static/*:
        forward:
          cookies: ["Auth"]
          headers: ["Authorization"]
      origins:
        - url: https://xxxxxxxxxxxxxxxxxx.us-west-2.elb.amazonaws.com
          protocolPolicy: https-only
          pathPatterns:
            sam/admin/*:
              minTTL: 0
              maxTTL: 86400
              defaultTTL: 60
              allowedHttpMethods:
                ["GET", "HEAD", "OPTIONS", "PUT", "POST", "PATCH", "DELETE"]
              forward: # optional
                headers: ["Host", "Referer"]
                cookies: "all"
                queryString: true
            scm/admin/*:
              minTTL: 0
              maxTTL: 86400
              defaultTTL: 60
              allowedHttpMethods:
                ["GET", "HEAD", "OPTIONS", "PUT", "POST", "PATCH", "DELETE"]
              forward: # optional
                headers: ["Host"]
                cookies: "all"
                queryString: true
        - url: https://xxxxxxxxxxxxxxxxxx.us-west-2.elb.amazonaws.com
          protocolPolicy: https-only
          pathPatterns:
            sam/*:
              minTTL: 0
              maxTTL: 86400
              defaultTTL: 60
              allowedHttpMethods:
                ["GET", "HEAD", "OPTIONS", "PUT", "POST", "PATCH", "DELETE"]
              forward: # optional
                headers: ["Host", "Referer"]
                cookies: "all"
                queryString: true
            scm/*:
              minTTL: 0
              maxTTL: 86400
              defaultTTL: 60
              allowedHttpMethods:
                ["GET", "HEAD", "OPTIONS", "PUT", "POST", "PATCH", "DELETE"]
              forward: # optional
                headers: ["Host", "Referer"]
                cookies: "all"
                queryString: true
        - url: https://xxxxxxxxxxxxxx.lambda-url.us-west-2.on.aws
          protocolPolicy: https-only
          pathPatterns:
            facade/*:
              minTTL: 0
              maxTTL: 86400
              defaultTTL: 60
              allowedHttpMethods:
                ["GET", "HEAD", "OPTIONS", "PUT", "POST", "PATCH", "DELETE"]
              forward: # optional
                headers: "none"
                cookies: "all"
                queryString: true
Walter
@McCo0L
any ideas?
Gareth McCumskey
@garethmcc
@McCo0L The nextjs component you are using isn't developed by Serverless but by the community of the next js component at https://github.com/serverless-nextjs/serverless-next.js. If you do not get an answer here you can probably get more people to assist there.
Sascha Kuhnigk
@sakuh:matrix.org
[m]
Hello, i am wondering if there is something like "cdk diff" for serverless available... can someone support here?
Gareth McCumskey
@garethmcc
@sakuh:matrix.org This looks like it can do the trick: https://github.com/nicka/serverless-plugin-diff
1 reply
Walter
@McCo0L
He @garethmcc , thanks for the advice. I raised an issue there to see if they give an answer, but thought about giving it a try here as it's possible that someone has an idea about what's going on with that error.
Carlos Alexandre
@calexandrepcjr
image.png
1 reply

Hi everyone,

I'm having a Circular dependency problem, and since yesterday, I searched through all the forum/gitter history, and I couldn't find anything that could help me. The error is:

The CloudFormation template is invalid: Circular dependency between resources: [12NestedStack, 1NestedStack, 11NestedStack, ApiGatewayResourceOfferingOfferingidVarRequirement, 19NestedStack, 2NestedStack, 10NestedStack, 20NestedStack, 9NestedStack, ApiGatewayDeployment1667571081871, 14NestedStack, 4NestedStack, ApiGatewayResourceOfferingOfferingidVarRequirementRequirementidVar]

I've tried changing the URIs, nothing worked.

When I generate locally the package, everything works. Also the serverless offline runs...
image.png
In the above image is the grep of the claimed resource in the generated pkg.
jhu portilho
@jhuportilho_twitter
Hi All, How can I integrate serverless framework using webpack plugin to send/publish the package into aws code artifact?
gitexp2050
@gitexp2050
Which is the best place to store image and server front-end quickly or fastly? Need to display 100 images in front-end
  1. S3
  2. Firebase
  3. DB
  4. Application Server folder webapps/project
  5. Shared folder common to application servers
  6. Folder in the Application Server outside the project (c:\ or d: drives)
  7. How many API calls to be sent to the server ? Each Image Each API call?
Gareth McCumskey
@garethmcc
@gitexp2050 S3 is far and way for me thebest place. It is specifically designed to help serve binary data super fast. You can also attach a CDN in front of it to cache this binary data in a point of presence closer to yuor customers as well. It also means that you have less concern with managing the underlying infrastructure and can just store and retrieve files with an infinit disk
gitexp2050
@gitexp2050

Mounting Server Folder - Accessing files through application server

I have 4 linux machines where applications runs on 3 and 1 linux file server where i have stored files.

  1. application server1 has port 192.168.1.101:8080
  2. application server2 has port 192.168.1.102:8080
  3. application server3 has port 192.168.1.103:8080
  4. file server has ip 195.168.1.108 - has images directory where images are stored

#4 has folder images and it has been mounted on all the application servers 1, 2, 3 as /images

assume common domain name configured: www.imageprocessing.com and internally routed with load balancing
to hit any of the application server

Please advise whether it works or how it works...Basically to serve/give a direct URL for the protected images for each users and different companies who uses same website/application...

frank-dspeed
@frank-dspeed:matrix.org
[m]
sure that works
the one holding the files is a serving function when it gets a request it random sends a action to one of the workers
and returns the workers result
it looks like
httpIncomingMessage => extract what i should do => request the action to run on a worker => waiting for the result then return to the sender of httpIncomingMessage
Jason Lane
@devblueray
I'm trying to use the serverless-fargate plugin and define a sidecar task in my service for the datadog agent. However, when I put the path to the image "public.ecr.aws/datadog/agent:latest" it tells me that it can't be found in provider.ecr.images. When I add it to that block with datadog: {uri: "public.ecr....."} and try referencing it with image: "datadog" in the task def, it says "invalid paramter at 'registryID'. thoughts?
selected-pixel-jameson
@selected-pixel-jameson
Hello all, I'm trying to setup my serverless project to deploy using AWS CodeBuild. Currently I have a profile designated within my serverless.yml file for local development and deployments. I'm wondering if there is a way to override the config profile setting when doing a deploy on the AWS CodeBuild instance?
Gareth McCumskey
@garethmcc
@selected-pixel-jameson You can instead setup AWS credentials as environment variables within the CI/CD build container: https://www.serverless.com/framework/docs/providers/aws/guide/credentials#using-aws-access-keys