serverless-framework

问题 I'm finding it hard to understand the difference between SAM template and Cloudformation template. I know that SAM template can be used to define Serverless Applications like Lambda, but how does that make it different from Cloudformation template? Is the syntax different? I can still specify the Lambda definitions in cloudformation template. So, my question is why should I care about SAM? Won't knowing about just cloud formation template be sufficient? 回答1: From CloudFormation's perspective,

问题 I've wrote a serverless.yml to deploy some lambdas and I'm using GSI in a specific API. If I run locally using serverless-offline, it's working but I'm facing an error when deploy the lambda: AccessDeniedException: User: arn:aws:sts::408462944160:assumed-role/telecom-integration-dev-us-east-1-lambdaRole/integration-dev-dialerStatistics is not authorized to perform: dynamodb:Query on resource: arn:aws:dynamodb:us-east-1:408462944160:table/integration-dialer-dev/index/other_dial_status-index

问题 I've wrote a serverless.yml to deploy some lambdas and I'm using GSI in a specific API. If I run locally using serverless-offline, it's working but I'm facing an error when deploy the lambda: AccessDeniedException: User: arn:aws:sts::408462944160:assumed-role/telecom-integration-dev-us-east-1-lambdaRole/integration-dev-dialerStatistics is not authorized to perform: dynamodb:Query on resource: arn:aws:dynamodb:us-east-1:408462944160:table/integration-dialer-dev/index/other_dial_status-index

问题 I've wrote a serverless.yml to deploy some lambdas and I'm using GSI in a specific API. If I run locally using serverless-offline, it's working but I'm facing an error when deploy the lambda: AccessDeniedException: User: arn:aws:sts::408462944160:assumed-role/telecom-integration-dev-us-east-1-lambdaRole/integration-dev-dialerStatistics is not authorized to perform: dynamodb:Query on resource: arn:aws:dynamodb:us-east-1:408462944160:table/integration-dialer-dev/index/other_dial_status-index

问题 I've wrote a serverless.yml to deploy some lambdas and I'm using GSI in a specific API. If I run locally using serverless-offline, it's working but I'm facing an error when deploy the lambda: AccessDeniedException: User: arn:aws:sts::408462944160:assumed-role/telecom-integration-dev-us-east-1-lambdaRole/integration-dev-dialerStatistics is not authorized to perform: dynamodb:Query on resource: arn:aws:dynamodb:us-east-1:408462944160:table/integration-dialer-dev/index/other_dial_status-index

问题 This question is pretty much the same as Serverless offline not getting route, but since that one was not answered I'm asking again. I'm trying to follow this article, https://medium.com/@awesome1888/how-to-use-serverless-locally-with-webpack-and-docker-5e268f71715, on how to deploy a Lambda function with Serverless. I have a directory with the following structure: > tree -I node_modules . ├── package-lock.json ├── package.json ├── serverless.yml ├── src │ ├── handler.js │ └── index.js └──

问题 i'm using DocumentClient for query. and using serverless framework with DynamoDb. i'm trying to query with BEGINS_WITH without providing any primary key. here is how my data looks like: [ { id: 1, some_string: "77281829121" }, { id: 2, some_string: "7712162hgvh" }, { id: 3, some_string: "7212121" } ] here is my serverless.yml [i.e Table config i guess]: Resources: IPRecord: Type: 'AWS::DynamoDB::Table' Properties: TableName: ${file(./serverless.js):Tables.IPRecord.name} BillingMode: PAY_PER

问题 i'm using DocumentClient for query. and using serverless framework with DynamoDb. i'm trying to query with BEGINS_WITH without providing any primary key. here is how my data looks like: [ { id: 1, some_string: "77281829121" }, { id: 2, some_string: "7712162hgvh" }, { id: 3, some_string: "7212121" } ] here is my serverless.yml [i.e Table config i guess]: Resources: IPRecord: Type: 'AWS::DynamoDB::Table' Properties: TableName: ${file(./serverless.js):Tables.IPRecord.name} BillingMode: PAY_PER

问题 I'm trying to integrate serverless to my circleci workflow. I tried first adding both, key and secret to AWS permissions , but that did not work. Then, I added key and secret to Environment variables and in my config file: sudo npm install -g serverless sls config credentials --provider aws --key $AWS_ACCESS_KEY_ID --secret $AWS_SECRET_ACCESS_KEY sls deploy -v But I see the same error: Serverless Error --------------------------------------- You are not currently logged in. Follow

问题 I'm trying to integrate serverless to my circleci workflow. I tried first adding both, key and secret to AWS permissions , but that did not work. Then, I added key and secret to Environment variables and in my config file: sudo npm install -g serverless sls config credentials --provider aws --key $AWS_ACCESS_KEY_ID --secret $AWS_SECRET_ACCESS_KEY sls deploy -v But I see the same error: Serverless Error --------------------------------------- You are not currently logged in. Follow