Service Quotas

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.

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; the starter already imports this enum.

Apply changes

pnpm landingzone:diff:all
pnpm landingzone:deploy:all

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. Removing an entry stops managing that quota and does not lower an approved limit.

Check each target account's Service Quotas console for the request status. A successful deployment does not mean AWS has approved the increase, so avoid depending on the higher limit during that deployment.

Use organizationAccountLimit for the management account's Organizations account quota. That setting is separate from this workload account list; re-run pnpm exec projen after editing landing-zone settings.