- 新しい順
- 投票が多い順
- コメントが多い順
As a new account, my initial limit was less than 10, even though the default value is 20. This lower limit was not reflected in my AWS Service Quotas console. Consequently, I had to request a limit increase twice.
The first time, my limit was raised to 10 instances. However, I had clearly communicated that my architecture required 12 instances. Therefore, I was unable to deploy the planned architecture after the first increase.
A few days later, I received a second increase, raising my limit to 50.
Interestingly, my AWS Service Quotas console still does not display the current limit for my Amazon Lightsail resources. AWS Support attributed this to “security policies”. It’s noteworthy that this policy only applies to Amazon Lightsail resources. All other AWS resources display both the default limit and the current limit. The reason behind this being a security policy remains unclear.
Consider that this is a summary that omits dozens of messages and calls with support, which each time had to consult the technical team before responding and could not immediately explain the reason for the limitations. All of this caused a delay in delivering the architecture to the client, making my devops team work over the weekend, and having to be told that there is no bug, and that the lack of display of limits was due first to my incorrect selection of the region (?!??!), then to a bug, and finally to a security policy. Sometimes it's better to admit that there's a problem.
As stated, your AWS account has default quotas, formerly referred to as limits, for each AWS service. Unless otherwise noted, each quota is Region-specific. You can request increases for some quotas, but not all quotas can be increased. Please reach out to the AWS Billing team to increase the limit. [+] https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html
Hi,
I noticed you were able to create more instances in your account. Was your issue resolved, or are you still running into limit issues?
UPDATE: after a support ticket the AWS team unlocked something on their side. This allowed me to run 8 instances. However, now I'm still blocked, because I need 4 more instances in order to complete the whole infrastructure.
Still waiting for a complete solution.