Rate Exceeded Error when deploying Helloworld Lambda using Serverless
See original GitHub issueThis is a Bug Report
Description
I have a simple Serverless application (see attachment) --hello world example.
When I try to deploy this lambda using serverless : serverless deploy -v I get the following:
Serverless Error ---------------------------------------
ServerlessError: Rate exceeded
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Forums: forum.serverless.com
Chat: gitter.im/serverless/serverless
Your Environment Information -----------------------------
OS: darwin
Node Version: 7.10.0
Serverless Version: 1.18.0
However, if I update serverless.yml with region as us-east-1 it works fine.
(see attachment for reproduction)
For bug reports:
- What went wrong? Rate Exceeded Error
- What did you expect should have happened? Lambda should have deployed
- What was the config you used?
Welcome to serverless. Read the docs
https://serverless.com/framework/docs/
Serverless.yml is the configuration the CLI
uses to deploy your code to your provider of choice
# The `service` block is the name of the service
service: serverless-hello-world
# The `provider` block defines where your service will be deployed
provider:
name: aws
runtime: nodejs6.10
region: us-west-2
# The `functions` block defines what code to deploy
functions:
helloWorld:
handler: handler.helloWorld
# The `events` block defines how to trigger the handler.helloWorld code
events:
- http:
path: hello-world
method: get
cors: true
- What stacktrace or error message from your provider did you see? ServerlessError: Rate exceeded
For feature proposals:
- What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us. Need to deploy lambda in us-west-2 since that contains all our subnets and security groups.
Additional Data
- Serverless Framework Version you’re using:
- Operating System: OSX
- Stack Trace:
- Provider Error messages:
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Serverless Error: Rate exceeded - Seed.run
This error happens when multiple Serverless services are being removed concurrently. It happens because Serverless Framework makes a series of ...
Read more >serverless/serverless - Gitter
Hey everyone, I'm having trouble with a consistent 500 error that I don't quite understand. I'm building a Lambda that connects to a...
Read more >Resolve Lambda throttling "Rate Exceeded" and 429 errors
Note: If a function is configured to have zero reserved concurrency, then the function is throttled because it can't process any events. Make ......
Read more >Deployment to AWS fails with "resource limit exceeded" - Elastic
The AWS limit on subscription filters is one per log group. If you've already deployed a Lambda function that monitors the log group,...
Read more >serverless deployment error - Code storage limit exceeded
The error could happen if you have a large number of Lambda functions that have been deployed many times. Each deployment creates a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This can also be an issue with your resource layout. AWS has rate limits e.g. for the creation of DynamoDB indices and databases simultaneously. CF is prone to hit these limits if the resources are not made dependent on each other which enforces serial construction.
For example if you have 3 DynamoDB tables that each create 3 indices, CF will create the table resources in parallel including the index creation. There is a high probability then, that it hits the account-wide limit of 5 simultaneous index creations during the stack resource setup. CF will fail in this case with a “Rate limit exceeded” exception - other in-account tasks not counted here (these also interfere).
@pmuens We are really hoping to start using Serverless framework. What is the status of this ticket?