AWS has denied a quota increase request for the Reference Architecture, now what?

[pete0emerson]

AWS has denied a request for a quota increase, and responded with this:

For this limit increase, I collaborated with our service team, since we must get their approval to continue, and they have explained to me that upon careful review and consideration, the new quota has not been approved.
Please keep in mind, that these limits are put in place to help you gradually ramp up activity and avoid large bills due to sudden, unexpected spikes. Once the Service Team has a broader window of usage on your account to review, they will be happy to reassess any requests.
These are some recommendations that you can keep in mind to build up a good usage history.
- Use your services about 90% of usage in that way we can request a limit increase.
- You can use a Free Tier in order to increase the activity in your account and the Service Team can analysis your request.
- You can wait for the next billing cycle then we can request again the limit increase.
- You can select resources that are not much expensive and scale down your usage.

How do I manage this to move our Reference Architecture forward?

---

Tracked in ticket #109504

[pete0emerson]

We programmatically request quota increases on your behalf in order to install and run the CI/CD pipeline. The API does not allow for us to add color and explain why whe need these quota increases. You may see that some of your requests are accepted, and some denied. You'll need to re-open each support issue and plead your case with AWS. Fortunately, doing so will usually resolve the problem successfully. You can use something like the following, customizing it to your specific account IDs and case numbers:

We are spooling up a Reference Architecture in AWS and putting an infrastructure CI/CD pipeline into six different accounts.
This infrastructure requires an increased usage of Lambda functions per our request.

The accounts, our internal label, support case #, and current status are listed below.

Two of these requests have already been approved, two are pending, and this one has been denied.

Please escalate and re-evaluate this case, because it blocks our ability to deploy our infrastructure into AWS.

Account: 012345678901
Internal use: shared
Case ID: 11122233344
Status: Denied

Account: 012345678902
Internal use: stage
Case ID: 11122233345
Status: Pending

Account: 012345678903
Internal use: prod
Case ID: 11122233346
Status: Pending

Account: 012345678904
Internal use: logs
Case ID: 11122233347
Status: Pending

Account: 012345678905
Internal use: security
Case ID: 11122233348
Status: Approved

Account: 012345678906
Internal use: dev
Case ID: 11122233349
Status: Approved