CodeBuild StartBuild fails: AccountLimitExceededException “Cannot have more than 0 builds in queue” (us-east-1)

The error you're encountering is related to the number of builds that can be queued in AWS CodeBuild. This is a separate limit from the "concurrently running builds" quota that you checked in Service Quotas.

When you receive the "Cannot have more than 0 builds in queue for the account" error, it suggests that your account currently has a queue limit of zero. This means that if all your concurrent build slots are in use, CodeBuild cannot queue additional builds.

There are a few recommended solutions:

1. Wait until other builds are complete before starting new ones. If you have builds running in other projects, they might be using up your concurrent build slots.

2. Increase the concurrent build limit for your project. This would allow more builds to run simultaneously, reducing the need for queuing.

3. Request a quota increase for the queued builds limit. Since this specific limit isn't directly exposed in the Service Quotas console, you'll need to contact AWS Support to request an increase. You can do this by:

• Opening the AWS Support Center
• Creating a new case
• Selecting "Service Limit Increase"
• Specifying CodeBuild as the service and requesting an increase to your queued builds limit

The valid range for the queued timeout setting is between 5 and 480 minutes, but this only applies once you have the ability to queue builds.

When starting builds in the future, you can also use the --queued-timeout-in-minutes-override parameter with the start-build command to specify how long a build should be allowed to remain in the queue before timing out.
Sources
Troubleshooting AWS CodeBuild - AWS CodeBuild
StartBuild - AWS CodeBuild