Amazon ECS 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 |
ecs.us-east-2.amazonaws.com ecs-fips.us-east-2.amazonaws.com |
HTTPS HTTPS |
US East (N. Virginia) | us-east-1 |
ecs.us-east-1.amazonaws.com ecs-fips.us-east-1.amazonaws.com |
HTTPS HTTPS |
US West (N. California) | us-west-1 |
ecs.us-west-1.amazonaws.com ecs-fips.us-west-1.amazonaws.com |
HTTPS HTTPS |
US West (Oregon) | us-west-2 |
ecs.us-west-2.amazonaws.com ecs-fips.us-west-2.amazonaws.com |
HTTPS HTTPS |
Africa (Cape Town) | af-south-1 | ecs.af-south-1.amazonaws.com | HTTPS |
Asia Pacific (Hong Kong) | ap-east-1 | ecs.ap-east-1.amazonaws.com | HTTPS |
Asia Pacific (Hyderabad) | ap-south-2 | ecs.ap-south-2.amazonaws.com | HTTPS |
Asia Pacific (Jakarta) | ap-southeast-3 | ecs.ap-southeast-3.amazonaws.com | HTTPS |
Asia Pacific (Malaysia) | ap-southeast-5 | ecs.ap-southeast-5.amazonaws.com | HTTPS |
Asia Pacific (Melbourne) | ap-southeast-4 | ecs.ap-southeast-4.amazonaws.com | HTTPS |
Asia Pacific (Mumbai) | ap-south-1 | ecs.ap-south-1.amazonaws.com | HTTPS |
Asia Pacific (Osaka) | ap-northeast-3 | ecs.ap-northeast-3.amazonaws.com | HTTPS |
Asia Pacific (Seoul) | ap-northeast-2 | ecs.ap-northeast-2.amazonaws.com | HTTPS |
Asia Pacific (Singapore) | ap-southeast-1 | ecs.ap-southeast-1.amazonaws.com | HTTPS |
Asia Pacific (Sydney) | ap-southeast-2 | ecs.ap-southeast-2.amazonaws.com | HTTPS |
Asia Pacific (Tokyo) | ap-northeast-1 | ecs.ap-northeast-1.amazonaws.com | HTTPS |
Canada (Central) | ca-central-1 | ecs.ca-central-1.amazonaws.com | HTTPS |
Canada West (Calgary) | ca-west-1 | ecs.ca-west-1.amazonaws.com | HTTPS |
Europe (Frankfurt) | eu-central-1 | ecs.eu-central-1.amazonaws.com | HTTPS |
Europe (Ireland) | eu-west-1 | ecs.eu-west-1.amazonaws.com | HTTPS |
Europe (London) | eu-west-2 | ecs.eu-west-2.amazonaws.com | HTTPS |
Europe (Milan) | eu-south-1 | ecs.eu-south-1.amazonaws.com | HTTPS |
Europe (Paris) | eu-west-3 | ecs.eu-west-3.amazonaws.com | HTTPS |
Europe (Spain) | eu-south-2 | ecs.eu-south-2.amazonaws.com | HTTPS |
Europe (Stockholm) | eu-north-1 | ecs.eu-north-1.amazonaws.com | HTTPS |
Europe (Zurich) | eu-central-2 | ecs.eu-central-2.amazonaws.com | HTTPS |
Israel (Tel Aviv) | il-central-1 | ecs.il-central-1.amazonaws.com | HTTPS |
Middle East (Bahrain) | me-south-1 | ecs.me-south-1.amazonaws.com | HTTPS |
Middle East (UAE) | me-central-1 | ecs.me-central-1.amazonaws.com | HTTPS |
South America (São Paulo) | sa-east-1 | ecs.sa-east-1.amazonaws.com | HTTPS |
AWS GovCloud (US-East) | us-gov-east-1 |
ecs.us-gov-east-1.amazonaws.com ecs-fips.us-gov-east-1.amazonaws.com |
HTTPS HTTPS |
AWS GovCloud (US-West) | us-gov-west-1 |
ecs.us-gov-west-1.amazonaws.com ecs-fips.us-gov-west-1.amazonaws.com |
HTTPS HTTPS |
These are the service endpoints that Amazon ECS Service Connect uses for Envoy management.
Region Name | Region | Endpoint | Protocol |
---|---|---|---|
US East (Ohio) | us-east-2 | ecs-sc.us-east-2.api.aws | HTTPS |
US East (N. Virginia) | us-east-1 | ecs-sc.us-east-1.api.aws | HTTPS |
US West (N. California) | us-west-1 | ecs-sc.us-west-1.api.aws | HTTPS |
US West (Oregon) | us-west-2 | ecs-sc.us-west-2.api.aws | HTTPS |
Africa (Cape Town) | af-south-1 | ecs-sc.af-south-1.api.aws | HTTPS |
Asia Pacific (Hong Kong) | ap-east-1 | ecs-sc.ap-east-1.api.aws | HTTPS |
Asia Pacific (Hyderabad) | ap-south-2 | ecs-sc.ap-south-2.api.aws | HTTPS |
Asia Pacific (Jakarta) | ap-southeast-3 | ecs-sc.ap-southeast-3.api.aws | HTTPS |
Asia Pacific (Malaysia) | ap-southeast-5 | ecs-sc.ap-southeast-5.api.aws | HTTPS |
Asia Pacific (Melbourne) | ap-southeast-4 | ecs-sc.ap-southeast-4.api.aws | HTTPS |
Asia Pacific (Mumbai) | ap-south-1 | ecs-sc.ap-south-1.api.aws | HTTPS |
Asia Pacific (Osaka) | ap-northeast-3 | ecs-sc.ap-northeast-3.api.aws | HTTPS |
Asia Pacific (Seoul) | ap-northeast-2 | ecs-sc.ap-northeast-2.api.aws | HTTPS |
Asia Pacific (Singapore) | ap-southeast-1 | ecs-sc.ap-southeast-1.api.aws | HTTPS |
Asia Pacific (Sydney) | ap-southeast-2 | ecs-sc.ap-southeast-2.api.aws | HTTPS |
Asia Pacific (Tokyo) | ap-northeast-1 | ecs-sc.ap-northeast-1.api.aws | HTTPS |
Canada (Central) | ca-central-1 | ecs-sc.ca-central-1.api.aws | HTTPS |
Canada West (Calgary) | ca-west-1 | ecs-sc.ca-west-1.api.aws | HTTPS |
Europe (Frankfurt) | eu-central-1 | ecs-sc.eu-central-1.api.aws | HTTPS |
Europe (Ireland) | eu-west-1 | ecs-sc.eu-west-1.api.aws | HTTPS |
Europe (London) | eu-west-2 | ecs-sc.eu-west-2.api.aws | HTTPS |
Europe (Milan) | eu-south-1 | ecs-sc.eu-south-1.api.aws | HTTPS |
Europe (Paris) | eu-west-3 | ecs-sc.eu-west-3.api.aws | HTTPS |
Europe (Spain) | eu-south-2 | ecs-sc.eu-south-2.api.aws | HTTPS |
Europe (Stockholm) | eu-north-1 | ecs-sc.eu-north-1.api.aws | HTTPS |
Europe (Zurich) | eu-central-2 | ecs-sc.eu-central-2.api.aws | HTTPS |
Israel (Tel Aviv) | il-central-1 | ecs-sc.il-central-1.api.aws | HTTPS |
Middle East (Bahrain) | me-south-1 | ecs-sc.me-south-1.api.aws | HTTPS |
Middle East (UAE) | me-central-1 | ecs-sc.me-central-1.api.aws | HTTPS |
South America (São Paulo) | sa-east-1 | ecs-sc.sa-east-1.api.aws | HTTPS |
Service quotas
The following are Amazon ECS service quotas.
Most of these service quotas, but not all, are listed under the Amazon Elastic Container Service (Amazon ECS) namespace in the Service Quotas console. To request a quota increase, see Requesting a quota increase in the Service Quotas User Guide.
Name | Default | Adjustable | Description |
---|---|---|---|
Capacity providers per cluster | Each supported Region: 20 | No | The maximum number of capacity providers that can be associated with a cluster. |
Classic Load Balancers per service | Each supported Region: 1 | No | The maximum number of Classic Load Balancers per service. |
Clusters per account | Each supported Region: 10,000 |
Yes |
Number of clusters per account |
Container instances per cluster | Each supported Region: 5,000 | No | Number of container instances per cluster |
Container instances per start-task | Each supported Region: 10 | No | The maximum number of container instances specified in a StartTask API action. |
Containers per task definition | Each supported Region: 10 | No | The maximum number of containers definitions within a task definition. |
ECS Exec sessions | Each supported Region: 1,000 | No | The maximum number of ECS Exec sessions per container. |
Rate of tasks launched by a service on AWS Fargate | Each supported Region: 500 | No | The maximum number of tasks that can be provisioned per service per minute on Fargate by the Amazon ECS service scheduler. |
Rate of tasks launched by a service on an Amazon EC2 or External instance | Each supported Region: 500 | No | The maximum number of tasks that can be provisioned per service per minute on an Amazon EC2 or External instance by the Amazon ECS service scheduler. |
Revisions per task definition family | Each supported Region: 1,000,000 | No | The maximum number of revisions per task definition family. Deregistering or deleting a task definition revision does not exclude it from being included in this limit. |
Security groups per awsvpcConfiguration | Each supported Region: 5 | No | The maximum number of security groups specified within an awsvpcConfiguration. |
Services per cluster | Each supported Region: 5,000 | No | The maximum number of services per cluster |
Services per namespace | Each supported Region: 100 |
Yes |
The maximum number of services that can be running within a namespace. |
Subnets per awsvpcConfiguration | Each supported Region: 16 | No | The maximum number of subnets specified within an awsvpcConfiguration. |
Tags per resource | Each supported Region: 50 | No | The maximum number of tags per resource. This applies to task definitions, clusters, tasks, and services. |
Target groups per service | Each supported Region: 5 | No | The maximum number of target groups per service, if using an Application Load Balancer or a Network Load Balancer. |
Task definition size | Each supported Region: 64 Kilobytes | No | The maximum size, in KiB, of a task definition. |
Tasks in PROVISIONING state per cluster | Each supported Region: 500 | No | The maximum number of tasks waiting in the PROVISIONING state per cluster. This quota only applies to tasks launched using an EC2 Auto Scaling group capacity provider. |
Tasks launched per run-task | Each supported Region: 10 | No | The maximum number of tasks that can be launched per RunTask API action. |
Tasks per service | Each supported Region: 5,000 | No | The maximum number of tasks per service (the desired count). |
Note
Services configured to use Amazon ECS service discovery have a limit of 1,000 tasks per service. This is due to the AWS Cloud Map service quota for the number of instances per service. For more information, see AWS Cloud Map service quotas in the Amazon Web Services General Reference.
Note
In practice, task launch rates are also dependent on other considerations such as container images to be downloaded and unpacked, health checks and other integrations enabled, such as registering tasks with a load balancer. You will see variations in task launch rates compared with the quotas represented above based on the features that you have enabled for your Amazon ECS services. For more information, see speeding up Amazon ECS deployments in the Amazon ECS Best Practices Guide.
AWS Fargate quotas
The following are Amazon ECS on AWS Fargate service quotas and are listed under the AWS Fargate service in the Service Quotas console.
New AWS accounts might have initial lower quotas that can increase over time. Fargate constantly monitors the account usage within each Region, and then automatically increases the quotas based on your usage. You can also request a quota increase for values that are shown as adjustable, see Requesting a quota increase in the Service Quotas User Guide.
Name | Default | Adjustable | Description |
---|---|---|---|
Fargate On-Demand Burst Launch Rate | Each supported Region: 100 |
Yes |
The maximum number of on-demand Amazon ECS tasks or Amazon EKS pods launched in a single burst (burst rate) in this account in the current region. |
Fargate On-Demand Sustained Launch Rate | Each supported Region: 20 |
Yes |
The maximum number of on-demand Amazon ECS tasks or Amazon EKS pods launched per second (sustained rate) in this account in the current region. |
Fargate On-Demand vCPU resource count | Each supported Region: 6 |
Yes |
The number of Fargate vCPUs running concurrently as Fargate On-Demand in this account in the current Region. |
Fargate Spot Burst Launch Rate | Each supported Region: 100 |
Yes |
The maximum number of Spot Amazon ECS tasks launched in a single burst (burst rate) in this account in the current region. |
Fargate Spot Sustained Launch Rate | Each supported Region: 20 |
Yes |
The maximum number of Spot Amazon ECS tasks launched per second (sustained rate) in this account in the current region. |
Fargate Spot vCPU resource count | Each supported Region: 6 |
Yes |
The number of Fargate vCPUs running concurrently as Fargate Spot in this account in the current Region. |
Note
The default values are the initial quotas set by AWS, which are separate from the actual applied quota value and maximum possible service quota. For more information, see Terminology in Service Quotas in the Service Quotas User Guide.
Note
Fargate additionally enforces Amazon ECS tasks and Amazon EKS pods launch rate limits. For more information, see AWS Fargate throttling quotas in the Amazon ECS Developer Guide.