Packer amazon-ebs quota / limit exceeded in CI

By Kaveh Alemi·Latchkey

AWS enforces service quotas such as running vCPUs per region. When a build launches an instance that would exceed the limit, EC2 refuses and Packer fails before provisioning.

What this error means

packer build fails with "VcpuLimitExceeded" or "InstanceLimitExceeded" when launching the source instance, often during parallel or high-frequency builds.

Error: Error launching source instance: VcpuLimitExceeded: You have requested more
vCPU capacity than your current vCPU limit of 32 allows for the instance bucket
that the specified instance type belongs to.
	status code: 400, request id: ...

Common causes

The region vCPU quota is reached

Concurrent builds or other running instances consume the vCPU quota, so a new build cannot launch.

A large instance type against a small limit

Building with a large instance type in an account with a low limit exceeds the quota on a single launch.

How to fix it

Reduce concurrency or instance size

1. Serialize builds so fewer instances run at once.
2. Use a smaller instance type for the build if it fits.
3. Re-run once capacity frees up.

Request a quota increase

Raise the relevant EC2 vCPU quota in Service Quotas for the build region so peak builds fit.

How to prevent it

• Limit parallel Packer builds against a single account and region.
• Right-size the build instance type.
• Request quota increases ahead of high-frequency build schedules.

Frequently asked questions

Related guides

References

• Terraform documentation
• GitHub Actions documentation