Amazon Simple Queue Service endpoints and quotas
This section lists the the service endpoints and service quotas for the service. To connect programmatically to an AWS service, you use an endpoint. For more information, see AWS service endpoints.
In addition to the standard AWS endpoints, some AWS services offer the following endpoints in some or all of the AWS Regions that the service is supported in:
IPv4 endpoints — These endpoints support only IPv4 requests and have the following format:
service-name
.region
.amazonaws.com.rproxy.goskope.comDual-stack endpoints — These endpoints support both IPv4 requests and IPv6 requests and have the following format:
service-name
.region
.api.awsFIPS endpoints — These endpoints comply with the Federal Information Processing Standards (FIPS) and can support either IPv4 requests or dual-stack (IPv4 and IPv6) requests. FIPS endpoints have the following format:
, whereservice-name
-fips.region
.ip-endpoint-type
ip-endpoint-type
isamazonaws.com
(for IPv4 requests) orapi.aws
(for IPv4 or IPv6 requests).
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.
Note
AWS recommends that you use Regional STS endpoints within your applications, and avoid using global (legacy) STS endpoints. Regional STS endpoints reduce latency, build in redundancy, and increase session token validity. For more information about configuring your applications to use a Regional STS endpoint, see AWS STS Regionalized endpoints in the AWS SDKs and Tools Reference Guide. For more information about global (legacy) AWS STS endpoints, including how to monitor for use of this type of endpoint, see How to use Regional AWS STS endpoints in the AWS Security blog.
Service endpoints
Amazon SQS
Region Name | Region | Endpoint | Protocol |
---|---|---|---|
US East (Ohio) | us-east-2 |
sqs.us-east-2.amazonaws.com sqs-fips.us-east-2.amazonaws.com |
HTTP and HTTPS HTTPS |
US East (N. Virginia) | us-east-1 |
sqs.us-east-1.amazonaws.com sqs-fips.us-east-1.amazonaws.com |
HTTP and HTTPS HTTPS |
US West (N. California) | us-west-1 |
sqs.us-west-1.amazonaws.com sqs-fips.us-west-1.amazonaws.com |
HTTP and HTTPS HTTPS |
US West (Oregon) | us-west-2 |
sqs.us-west-2.amazonaws.com sqs-fips.us-west-2.amazonaws.com |
HTTP and HTTPS HTTPS |
Africa (Cape Town) | af-south-1 | sqs.af-south-1.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Hong Kong) | ap-east-1 | sqs.ap-east-1.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Hyderabad) | ap-south-2 | sqs.ap-south-2.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Jakarta) | ap-southeast-3 | sqs.ap-southeast-3.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Malaysia) | ap-southeast-5 | sqs.ap-southeast-5.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Melbourne) | ap-southeast-4 | sqs.ap-southeast-4.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Mumbai) | ap-south-1 | sqs.ap-south-1.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Osaka) | ap-northeast-3 | sqs.ap-northeast-3.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Seoul) | ap-northeast-2 | sqs.ap-northeast-2.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Singapore) | ap-southeast-1 | sqs.ap-southeast-1.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Sydney) | ap-southeast-2 | sqs.ap-southeast-2.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Thailand) | ap-southeast-7 | sqs.ap-southeast-7.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Tokyo) | ap-northeast-1 | sqs.ap-northeast-1.amazonaws.com | HTTP and HTTPS |
Canada (Central) | ca-central-1 | sqs.ca-central-1.amazonaws.com | HTTP and HTTPS |
Canada West (Calgary) | ca-west-1 | sqs.ca-west-1.amazonaws.com | HTTP and HTTPS |
Europe (Frankfurt) | eu-central-1 | sqs.eu-central-1.amazonaws.com | HTTP and HTTPS |
Europe (Ireland) | eu-west-1 | sqs.eu-west-1.amazonaws.com | HTTP and HTTPS |
Europe (London) | eu-west-2 | sqs.eu-west-2.amazonaws.com | HTTP and HTTPS |
Europe (Milan) | eu-south-1 | sqs.eu-south-1.amazonaws.com | HTTP and HTTPS |
Europe (Paris) | eu-west-3 | sqs.eu-west-3.amazonaws.com | HTTP and HTTPS |
Europe (Spain) | eu-south-2 | sqs.eu-south-2.amazonaws.com | HTTP and HTTPS |
Europe (Stockholm) | eu-north-1 | sqs.eu-north-1.amazonaws.com | HTTP and HTTPS |
Europe (Zurich) | eu-central-2 | sqs.eu-central-2.amazonaws.com | HTTP and HTTPS |
Israel (Tel Aviv) | il-central-1 | sqs.il-central-1.amazonaws.com | HTTP and HTTPS |
Mexico (Central) | mx-central-1 | sqs.mx-central-1.amazonaws.com | HTTP and HTTPS |
Middle East (Bahrain) | me-south-1 | sqs.me-south-1.amazonaws.com | HTTP and HTTPS |
Middle East (UAE) | me-central-1 | sqs.me-central-1.amazonaws.com | HTTP and HTTPS |
South America (São Paulo) | sa-east-1 | sqs.sa-east-1.amazonaws.com | HTTP and HTTPS |
AWS GovCloud (US-East) | us-gov-east-1 | sqs.us-gov-east-1.amazonaws.com | HTTP and HTTPS |
AWS GovCloud (US-West) | us-gov-west-1 | sqs.us-gov-west-1.amazonaws.com | HTTP and HTTPS |
Legacy endpoints
If you use the AWS CLI or SDK for Python, you can use the following legacy endpoints.
Region Name | Region | Endpoint | Protocol |
---|---|---|---|
US East (Ohio) | us-east-2 | us-east-2.queue.amazonaws.com | HTTP and HTTPS |
US East (N. Virginia) | us-east-1 | queue.amazonaws.com | HTTP and HTTPS |
US West (N. California) | us-west-1 | us-west-1.queue.amazonaws.com | HTTP and HTTPS |
US West (Oregon) | us-west-2 | us-west-2.queue.amazonaws.com | HTTP and HTTPS |
Africa (Cape Town) | af-south-1 | af-south-1.queue.amazonaws.com | HTTP |
Asia Pacific (Mumbai) | ap-south-1 | ap-south-1.queue.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Osaka) | ap-northeast-3 | ap-northeast-3.queue.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Seoul) | ap-northeast-2 | ap-northeast-2.queue.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Singapore) | ap-southeast-1 | ap-southeast-1.queue.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Sydney) | ap-southeast-2 | ap-southeast-2.queue.amazonaws.com | HTTP and HTTPS |
Asia Pacific (Tokyo) | ap-northeast-1 | ap-northeast-1.queue.amazonaws.com | HTTP and HTTPS |
Canada (Central) | ca-central-1 | ca-central-1.queue.amazonaws.com | HTTP and HTTPS |
China (Beijing) | cn-north-1 | cn-north-1.queue.amazonaws.com | HTTP and HTTPS |
China (Ningxia) | cn-northwest-1 | cn-northwest-1.queue.amazonaws.com | HTTP and HTTPS |
Europe (Frankfurt) | eu-central-1 | eu-central-1.queue.amazonaws.com | HTTP and HTTPS |
Europe (Ireland) | eu-west-1 | eu-west-1.queue.amazonaws.com | HTTP and HTTPS |
Europe (London) | eu-west-2 | eu-west-2.queue.amazonaws.com | HTTP and HTTPS |
Europe (Paris) | eu-west-3 | eu-west-3.queue.amazonaws.com | HTTP and HTTPS |
Europe (Stockholm) | eu-north-1 | eu-north-1.queue.amazonaws.com | HTTP and HTTPS |
South America (São Paulo) | sa-east-1 | sa-east-1.queue.amazonaws.com | HTTP and HTTPS |
Service quotas
Name | Default | Adjustable | Description |
---|---|---|---|
Actions per Queue Policy | Each supported Region: 7 | No | The number of actions in a queue policy. |
Attributes per Message | Each supported Region: 10 | No | The number of attributes added to a message. |
Batched Message ID Length | Each supported Region: 80 | No | The length of a batched message ID. |
Batched Message Throughput for FIFO Queues | Each supported Region: 3,000 | No | The number of batched transactions per second (TPS) for FIFO queues. |
Batched Message High Throughput for FIFO Queues | Supported Regions (US East (N. Virginia), US West (Oregon), and Europe (Ireland)): 700,000 Europe (Frankfurt) and US East (Ohio): 180,000 Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney) and Asia Pacific (Tokyo): 90,000 Europe (London) and South America (São Paulo):45,000 All other supported Regions: 24,000 |
No | The number of batched transactions per second (TPS) for FIFO queues. |
Conditions per Queue Policy | Each supported Region: 10 | No | The number of conditions in a queue policy. |
In-Flight Messages per FIFO Queue | Each supported Region: 20,000 | No | The number of in-flight messages in a FIFO queue. |
In-Flight Messages per Standard Queue | Each supported Region: 120,000 | Yes |
The number of in-flight messages in a standard queue. |
Message Invisibility Period | Each supported Region: 0 Seconds | No | The length of time, in seconds, for which Amazon SQS retains a message if it isn't deleted. The maximum is 14 days (1,209,600 seconds). |
Message Size | Each supported Region: 256 Kilobytes | No | The size of a message, in kilobytes. |
Message Size in Amazon S3 Bucket | Each supported Region: 2 Gigabytes | No | The size of a message, in gigabytes, in an Amazon S3 bucket. |
Messages per Batch | Each supported Region: 10 | No | The number of messages in a message batch. |
Principals per Queue Policy | Each supported Region: 50 | No | The length of time, in minutes, by which to delay the initial delivery of messages to a queue. |
Queue Name Length | Each supported Region: 80 | No | The queue name length. |
Queue Policy Size | Each supported Region: 8,192 Bytes | No | The size, in bytes, of a queue policy. |
Statements per Queue Policy | Each supported Region: 20 | No | The number of tags added to a queue. |
UTF-8 Queue Tag Key Length | Each supported Region: 128 | No | The length of a UTF-8 queue tag key. |
UTF-8 Queue Tag Value Length | Each supported Region: 256 | No | The length of a UTF-8 queue tag value. |
Unbatched Message Throughput for FIFO Queues | Each supported Region: 300 | No | The number of unbatched transactions per second (TPS) for FIFO queues. |
Unbatched Message High Throughput for FIFO Queues |
Supported Regions (US East (N. Virginia), US West (Oregon), and Europe (Ireland)): 70,000 US East (Ohio) and Europe (Frankfurt): 18,000 Supported Regions (Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo)): 9,000 Europe (London) and South America (São Paulo): 4,500 All other supported Regions: 2,400 |
No | The number of unbatched transactions per second (TPS) for FIFO queues. |
For more information, see Amazon SQS
quotas in the Amazon Simple Queue Service Developer Guide and the Limits and restrictions