Default Lambda concurrent executions value only 50
I have created new AWS Org and some sub-accounts, and noticed that each account, by default, only had 50 concurrent executions applied. I was under impression that default quota is 1000 https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html
Why only 50 was applied?
Per documentations, "A few new AWS accounts might start out with limits that are lower than these defaults. AWS monitors usage and raises your limits automatically based on your usage.".
"A few new" is interesting amount, as in pass few months I have setup 10+ new accounts, and ALL OF THEM have 50 by default.
I now asked support increase to 100 on one of the accounts. I still can't edit Lambda's Reserve concurrency, it just says "The unreserved account concurrency can't go below 100." Before, error was "The unreserved account concurrency can't go below 50." I tried defining concurrency on account,where value is 1000, no any error comes.
Am I right, that actually minimum available unreserved account concurrency is 100? If 100 is minimum, why in first place only 50 was applied on accounts?
Error creating CUDOS Dashboard using CloudFormation (AWSCURInitializer )Accepted Answerasked 5 months ago
Cannot Get CodeBuild to Build More Than 1 Concurrent BuildAccepted Answerasked 2 months ago
Combining two accounts that once had consolidated billingasked 2 years ago
New account has subnets, security groups, and VPCs in 17 regions.asked 17 days ago
Lambda access deniedasked 5 months ago
Lambda limits for concurrent executionsasked 2 years ago
Default Lambda concurrent executions value only 50asked 23 days ago
How to deploy AWS Content Analysis using CloudFormation template?Accepted Answerasked 4 months ago
How many concurrent total limit of users in IVS Defaultasked 2 months ago
Cannot have more than 0 active builds - AccountLimitExceededExceptionasked 5 years ago