AWS CodeDeploy endpoints and quotas - AWS General Reference

AWS CodeDeploy endpoints and quotas

The following are the service endpoints and service quotas for this service. To connect programmatically to an AWS service, you use an endpoint. In addition to the standard AWS endpoints, some AWS services offer FIPS endpoints in selected Regions. For more information, see AWS service endpoints. Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. For more information, see AWS service quotas.

Service endpoints

Region Name Region Endpoint Protocol
US East (Ohio) us-east-2

codedeploy.us-east-2.amazonaws.com

codedeploy-fips.us-east-2.amazonaws.com

HTTPS

HTTPS

US East (N. Virginia) us-east-1

codedeploy.us-east-1.amazonaws.com

codedeploy-fips.us-east-1.amazonaws.com

HTTPS

HTTPS

US West (N. California) us-west-1

codedeploy.us-west-1.amazonaws.com

codedeploy-fips.us-west-1.amazonaws.com

HTTPS

HTTPS

US West (Oregon) us-west-2

codedeploy.us-west-2.amazonaws.com

codedeploy-fips.us-west-2.amazonaws.com

HTTPS

HTTPS

Africa (Cape Town) af-south-1 codedeploy.af-south-1.amazonaws.com HTTPS
Asia Pacific (Hong Kong) ap-east-1 codedeploy.ap-east-1.amazonaws.com HTTPS
Asia Pacific (Jakarta) ap-southeast-3 codedeploy.ap-southeast-3.amazonaws.com HTTPS
Asia Pacific (Mumbai) ap-south-1 codedeploy.ap-south-1.amazonaws.com HTTPS
Asia Pacific (Osaka) ap-northeast-3 codedeploy.ap-northeast-3.amazonaws.com HTTPS
Asia Pacific (Seoul) ap-northeast-2 codedeploy.ap-northeast-2.amazonaws.com HTTPS
Asia Pacific (Singapore) ap-southeast-1 codedeploy.ap-southeast-1.amazonaws.com HTTPS
Asia Pacific (Sydney) ap-southeast-2 codedeploy.ap-southeast-2.amazonaws.com HTTPS
Asia Pacific (Tokyo) ap-northeast-1 codedeploy.ap-northeast-1.amazonaws.com HTTPS
Canada (Central) ca-central-1 codedeploy.ca-central-1.amazonaws.com HTTPS
Europe (Frankfurt) eu-central-1 codedeploy.eu-central-1.amazonaws.com HTTPS
Europe (Ireland) eu-west-1 codedeploy.eu-west-1.amazonaws.com HTTPS
Europe (London) eu-west-2 codedeploy.eu-west-2.amazonaws.com HTTPS
Europe (Milan) eu-south-1 codedeploy.eu-south-1.amazonaws.com HTTPS
Europe (Paris) eu-west-3 codedeploy.eu-west-3.amazonaws.com HTTPS
Europe (Stockholm) eu-north-1 codedeploy.eu-north-1.amazonaws.com HTTPS
Middle East (Bahrain) me-south-1 codedeploy.me-south-1.amazonaws.com HTTPS
Middle East (UAE) me-central-1 codedeploy.me-central-1.amazonaws.com HTTPS
South America (São Paulo) sa-east-1 codedeploy.sa-east-1.amazonaws.com HTTPS
AWS GovCloud (US-East) us-gov-east-1

codedeploy.us-gov-east-1.amazonaws.com

codedeploy-fips.us-gov-east-1.amazonaws.com

HTTPS

HTTPS

AWS GovCloud (US-West) us-gov-west-1

codedeploy.us-gov-west-1.amazonaws.com

codedeploy-fips.us-gov-west-1.amazonaws.com

HTTPS

HTTPS

Service quotas

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
Auto Scaling groups in a deployment group Each supported Region: 10 No Maximum number of Amazon EC2 Auto Scaling groups in a deployment group
Concurrent deployments per account Each supported Region: 1,000 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: 8 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

For more information, see Quotas in CodeDeploy in the AWS CodeDeploy User Guide.