CodeDeploy quotas
The following tables describe quotas in CodeDeploy.
Note
The EC2/On-Premises in-place deployment run in hours limit varies. For custom deployment configurations created before June 2023, the limit is 8 hours. For custom deployment configurations created in June 2023 or later, the limit is 12 hours. For pre-defined deployment configurations, the limit is 12 hours.
| Name | Default | Adjustable | Description |
|---|---|---|---|
| AWS Lambda deployment run in hours | Each supported Region: 50 | No | Maximum number of hours an AWS Lambda deployment can run (48 hours for the maximum time between the first and last traffic shift plus one hour for each of two possible lifecycle hooks) |
| Applications associated per account per region | Each supported Region: 1,000 |
Yes |
The maximum number of applications associated with an AWS account in a single region |
| Associated alarms per deployment group | Each supported Region: 50 |
Yes |
The maximum number of alarms associated with a deployment group |
| Auto Scaling groups in a deployment group | Each supported Region: 10 |
Yes |
Maximum number of Amazon EC2 Auto Scaling groups in a deployment group |
| Concurrent deployments per account | Each supported Region: 1,300 |
Yes |
Maximum number of concurrent deployments associated with an AWS account. Each deployment to a scaled-up Amazon EC2 instance in an Amazon EC2 Auto Scaling group counts as a single concurrent deployment for each application that the EC2 instance is associated with. |
| Concurrent deployments per deployment group | Each supported Region: 1 | No | Maximum number of concurrent deployments to a deployment group. This limit prevents concurrent deployments of the same application to the same deployment group. |
| Custom deployment configurations per account | Each supported Region: 50 | No | Maximum number of custom deployment configurations associated with an AWS account |
| Deployment groups associated with a single application | Each supported Region: 1,000 |
Yes |
Maximum number of deployment groups associated with a single application |
| EC2/On-Premises blue/green deployment run in hours | Each supported Region: 109 | No | Maximum number of hours an EC2/On-Premises blue/green deployment can run (48 hours for each of the above two limits plus one hour for each of 13 possible lifecycle events) |
| EC2/On-Premises in-place deployment run in hours | Each supported Region: 12 | No | Maximum number of hours an EC2/On-Premises in-place deployment can run |
| Event notification triggers in a deployment group | Each supported Region: 10 |
Yes |
Maximum number of event notification triggers in a deployment group |
| GitHub connection tokens per account | Each supported Region: 25 | No | Maximum number of GitHub connection tokens for a single AWS account |
| Hours between the completion of a deployment and the termination of the original instances during an EC2/On-Premises blue/green deployment | Each supported Region: 48 | No | Maximum number of hours between the completion of a deployment and the termination of the original instances during an EC2/On-Premises blue/green deployment |
| Hours between the deployment of a revision and when traffic shifts to the replacement instances during an EC2/On-Premises blue/green deployment | Each supported Region: 48 | No | Maximum number of hours between the deployment of a revision and when traffic shifts to the replacement instances during an EC2/On-Premises blue/green deployment |
| Instances count per deployment |
us-east-1: 2,000 Each of the other supported Regions: 1,000 |
Yes |
Maximum number of instances in a single deployment |
| Minutes a blue/green deployment can wait after a successful deployment before terminating instances from the original deployment | Each supported Region: 2,800 | No | Maximum number of minutes a blue/green deployment can wait after a successful deployment before terminating instances from the original deployment |
| Minutes between the first and last traffic shift during an AWS Lambda canary or linear deployment | Each supported Region: 2,880 | No | Maximum number of minutes between the first and last traffic shift during an AWS Lambda canary or linear deployment |
| Minutes until a deployment fails if a lifecycle event doesnt start | Each supported Region: 5 | No | Maximum number of minutes until a deployment fails if a lifecycle event doesnt start after (1) a deployment is triggered by using the console or the AWS CLI create-deployment command, or (2) the previous lifecycle event is completed. |
| Number of deployment groups that can be associated with an Amazon ECS service | Each supported Region: 1 | No | Maximum number of deployment groups that can be associated with an Amazon ECS service |
| Number of instances that can be passed to the BatchGetOnPremisesInstances API action | Each supported Region: 100 | No | Maximum number of instances that can be passed to the BatchGetOnPremisesInstances API action |
| Number of instances used by concurrent deployments that are in progress per account |
us-east-1: 3,000 Each of the other supported Regions: 1,000 |
Yes |
Maximum number of instances that can be used by concurrent deployments that are in progress and associated with one account |
| Number of listeners for a traffic route during an Amazon ECS deployment | Each supported Region: 1 | No | Maximum number of listeners for a traffic route during an Amazon ECS deployment |
| Seconds until a deployment lifecycle event fails if not completed | Each supported Region: 3,600 Seconds | No | Maximum number of seconds until a deployment lifecycle event fails if not completed |
| Size of deployment group name | Each supported Region: 100 | No | Maximum number of characters in a deployment group name |
| Size of tag key | Each supported Region: 128 | No | Maximum number of characters in a tag key |
| Size of tag value | Each supported Region: 256 | No | Maximum number of characters in a tag value |
| Tags in a deployment group | Each supported Region: 10 | No | Maximum number of tags in a deployment group |
| Traffic that can be shifted in one increment during an AWS Lambda deployment | Each supported Region: 99 | No | Maximum percentage of traffic that can be shifted in one increment during an AWS Lambda deployment |
