Amazon CodeDeploy · Rate Limits

Amazon CodeDeploy Rate Limits

Amazon CodeDeploy Rate Limits is the rate-limit profile for Amazon CodeDeploy on the APIs.io network — every limit transcribed verbatim from the provider’s own documentation on 2026-11-11.

It captures 33 rate-limit definitions, including AWS Lambda deployment run in hours — Each supported Region: 50; Applications associated per account per region — Each supported Region: 1,000; Associated alarms per deployment group — Each supported Region: 50.

Tagged areas include Amazon, Amazon Web Services, Deployment, DevOps, and CI/CD.

33 Limits

Transcribed from the provider's documentation on 2026-11-11 — docs.aws.amazon.com/codedeploy/latest/userguide/limits.md.

View Source

AmazonAmazon Web ServicesDeploymentDevOpsCI/CDRelease ManagementBlue/Green DeploymentDeveloper Tools

Limits

AWS Lambda deployment run in hours per-account per-region

Each supported Region: 50

Applications associated per account per region per-account per-region

Each supported Region: 1,000

Associated alarms per deployment group per-account per-region

Each supported Region: 50

Auto Scaling groups in a deployment group per-account per-region

Each supported Region: 10

Concurrent deployments per account per-account per-region

Each supported Region: 1,300

Concurrent deployments per deployment group per-account per-region

Each supported Region: 1

Custom deployment configurations per account per-account per-region

Each supported Region: 50

Deployment groups associated with a single application per-account per-region

Each supported Region: 1,000

EC2/On-Premises blue/green deployment run in hours per-account per-region

Each supported Region: 109

EC2/On-Premises in-place deployment run in hours per-account per-region

Each supported Region: 12

Event notification triggers in a deployment group per-account per-region

Each supported Region: 10

GitHub connection tokens per account per-account per-region

Each supported Region: 25

Hours between the completion of a deployment and the termination of the original instances during an EC2/On-Premises blue/green deployment per-account per-region

Each supported Region: 48

Hours between the deployment of a revision and when traffic shifts to the replacement instances during an EC2/On-Premises blue/green deployment per-account per-region

Each supported Region: 48

Instances count per deployment per-account per-region

us-east-1: 2,000

Instances count per deployment per-account per-region

us-east-2: 2,000

Instances count per deployment per-account per-region

us-west-2: 2,000

Instances count per deployment per-account per-region

eu-central-1: 2,000

Instances count per deployment per-account per-region

Each of the other supported Regions: 1,000

Minutes a blue/green deployment can wait after a successful deployment before terminating instances from the original deployment per-account per-region

Each supported Region: 2,800

Minutes between the first and last traffic shift during an AWS Lambda canary or linear deployment per-account per-region

Each supported Region: 2,880

Minutes until a deployment fails if a lifecycle event doesnt start per-account per-region

Each supported Region: 5

Number of deployment groups that can be associated with an Amazon ECS service per-account per-region

Each supported Region: 1

Number of instances that can be passed to the BatchGetOnPremisesInstances API action per-account per-region

Each supported Region: 100

BatchGetOnPremisesInstances

Number of instances used by concurrent deployments that are in progress per account per-account per-region

us-east-1: 3,000

Number of instances used by concurrent deployments that are in progress per account per-account per-region

Each of the other supported Regions: 1,000

Number of listeners for a traffic route during an Amazon ECS deployment per-account per-region

Each supported Region: 1

Seconds until a deployment lifecycle event fails if not completed per-account per-region

Each supported Region: 3,600 Seconds

Size of deployment group name per-account per-region

Each supported Region: 100

Size of tag key per-account per-region

Each supported Region: 128

Size of tag value per-account per-region

Each supported Region: 256

Tags in a deployment group per-account per-region

Each supported Region: 10

Traffic that can be shifted in one increment during an AWS Lambda deployment per-account per-region

Each supported Region: 99

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this

find_rate_limitsBrowse and filter every rate limit in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This rate limit

curl "https://apis.io/api/v1/rate-limits/amazon-codedeploy-rate-limits"

All rate limits

curl "https://apis.io/api/v1/rate-limits?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.