1 Answer
- Newest
- Most votes
- Most comments
0
Please take a look at the Lambda quotas page - https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html
In particular, note this message:
Important New AWS accounts have reduced concurrency and memory quotas. AWS raises these quotas automatically based on your usage. You can also request a quota increase.
It is possible that you are running into account level quotas for lambda. Please request increases in quotas for your account or work with AWS support.
Relevant content
- asked 2 years ago
- Accepted Answerasked 6 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
Hi @Indranil, By reading your answer i understood that my problem could be with cloudwatch api throttling. Is there a way to extend the limits for cloudwatch api calls?
Here is the link to Cloudwatch quotas - https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_limits.html
If you need to increase quotas, you will need to reach out to AWS Support or work through your assigned AWS account team, if there is one.