src/config/service-quotas.ts lists the quota increases requested by the Service Quotas StackSet for accounts in the Development, Production, and Security OUs. Regional requests apply in every active Region. The starter requests 2,000 concurrent Lambda executions.
Options
The exported serviceQuotaRequests is a Readonly<Record<string, IncreaseServiceQuotaConstructProps>>. Each key identifies one request and should stay unchanged when you raise its requested value.
| Field | Type | Required | Description |
|---|---|---|---|
serviceCode | string | Yes | Service Quotas namespace, such as lambda. Must match the quota's service. |
quotaCode | string | Yes | Quota identifier, such as L-B99A9384 for concurrent Lambda executions. |
desiredValue | number | Yes | New quota value to request. Approval is asynchronous. |
scope | ServiceQuotaScope | No | Defaults to ServiceQuotaScope.REGIONAL. Use ServiceQuotaScope.GLOBAL for an account-wide quota requested once per account. |
Find the service and quota codes in the AWS Service Quotas console. Confirm that the quota is adjustable before adding a request.
Starter configuration
export const serviceQuotaRequests: Readonly<Record<string, IncreaseServiceQuotaConstructProps>> = {
IncreaseLambdaConcurrentExecutionsQuota: {
serviceCode: 'lambda',
quotaCode: 'L-B99A9384',
desiredValue: 2000,
},
};
Add another key to request a different quota. Keep an existing key when changing desiredValue. For global quotas, add scope: ServiceQuotaScope.GLOBAL to the entry, and import ServiceQuotaScope from @towardsthecloud/cdk-landing-zone-constructs in service-quotas.ts.
Apply changes
pnpm landingzone:diff:all
pnpm landingzone:deploy:all
Things to know
- Requests are filed once. The landing zone requests an increase only when the current or already-requested value is lower than
desiredValue. Repeated deployments with the same value do not request it again. - Approval is asynchronous. A successful deployment does not mean AWS has approved the increase. Check each target account's Service Quotas console for the request status, and do not depend on the higher limit during that deployment. See requesting a quota increase.
- Only adjustable quotas can be raised. Confirm the quota shows as adjustable before adding a request.
- Removing an entry leaves the quota as it is. The landing zone stops managing that quota and does not lower a limit AWS already granted. Adding the entry back files a request again only if the current or pending value is lower than
desiredValue. - Targets. Requests are filed from every account in the Development, Production, and Security OUs, in every active Region. The management account is not included; use
organizationAccountLimitfor its Organizations account quota, and re-runpnpm exec projenafter editing landing-zone settings.