---

Amazon SQS Functionality

• Developers can create an unlimited number of Amazon SQS queues with an unlimited number of messages.

• A queue can be created in any region.
• The message payload can contain up to 256KB of text in any format. Each 64KB ‘chunk’ of payload is billed as 1 request. For example, a single API call with a 256KB payload will be billed as four requests.
• Messages can be sent, received or deleted in batches of up to 10 messages or 256KB. Batches cost the same amount as single messages, meaning SQS can be even more cost effective for customers that use batching.
• Long polling reduces extraneous polling to help you minimize cost while receiving new messages as quickly as possible. When your queue is empty, long-poll requests wait up to 20 seconds for the next message to arrive. Long poll requests cost the same amount as regular requests.
• Messages can be retained in queues for up to 14 days.
• Messages can be sent and read simultaneously.

• When a message is received, it becomes “locked” while being processed. This keeps other computers from processing the message simultaneously. If the message processing fails, the lock will expire and the message will be available again. In the case where the application needs more time for processing, the “lock” timeout can be changed dynamically via the ChangeMessageVisibility operation.
• Developers can securely share Amazon SQS queues with others. Queues can be shared with other AWS accounts and Anonymously. Queue sharing can also be restricted by IP address and time-of-day.
• When combined with Amazon Simple Notification Service (SNS), developers can 'fanout' identical messages to multiple SQS queues in parallel. When developers want to process the messages in multiple passes, fanout helps complete this more quickly, and with fewer delays due to bottlenecks at any one stage. Fanout also makes it easier to record duplicate copies of your messages, for example in different databases.

---

Service Highlights

Amazon SQS provides significant advantages over the complexity of home-grown messaging systems or the ongoing expense of licensed or hosted systems.

Reliable – Amazon SQS runs within Amazon’s high-availability data centers, so queues will be available whenever applications need them. To prevent messages from being lost or becoming unavailable, all messages are stored redundantly across multiple servers and data centers.

Simple – Developers can get started with Amazon SQS by using only five APIs: CreateQueue, SendMessage, ReceiveMessage, ChangeMessageVisibility, and DeleteMessage. Additional APIs are available to provide advanced functionality.

Scalable – Amazon SQS was designed to enable an unlimited number of services to read and write an unlimited number of messages at any time.

Secure – Authentication mechanisms are provided to ensure that messages stored in Amazon SQS queues are secured against unauthorized access.

Inexpensive – No up-front or fixed expenses. The only costs of sending messages through Amazon SQS are small per-request handling fees and data transfer fees.

---

Using Amazon SQS with Other AWS Infrastructure Web Services

Amazon SQS can be used with other AWS Services such as Redshift, DynamoDB, RDS, EC2, and S3, to make distributed applications more scalable and reliable. Below are some common design patterns:

• Work Queues: Decouple components of a distributed application that may not all process the same amount of work simultaneously.
• Buffer and Batch Operations: Add scalability and reliability to your architecture, and smooth out temporary volume spikes without losing messages or increasing latency.
• Request Offloading: Move slow operations off of interactive request paths by enqueing the request.
• Fanout: Combine SQS with Simple Notification Service (SNS) to send identical copies of a message to multiple queues in parallel for simultaneous processing.

---

Pricing

Pay only for what you use. There is no minimum fee. Estimate your monthly bill using the AWS Simple Monthly Calculator.

Requests

• $0.50 per 1 million Amazon SQS Requests ($0.0000005 per SQS Request)
• Batches of up to 10 messages or 256KB per request cost the same amount as single messages.
• Each 64KB ‘chunk’ of payload is billed as 1 request. For example, a single API call with a 256KB payload will be billed as four requests.

Amazon SQS requests are: CreateQueue, ListQueues, DeleteQueue, SendMessage, SendMessageBatch, ReceiveMessage, ChangeMessageVisibility, ChangeMessageVisibilityBatch, DeleteMessage, DeleteMessageBatch, SetQueueAttributes, GetQueueAttributes, GetQueueUrl, AddPermission, and RemovePermission.

Data Transfer**

The pricing below is based on data transferred “in” and “out” of Amazon SQS.

Data transfer “in” and “out” refers to transfer into and out of Amazon SQS. Data transferred between Amazon SQS and Amazon EC2 within a single region is free of charge (i.e., $0.00 per GB). Data transferred between Amazon SQS and Amazon EC2 in different regions will be charged at Internet Data Transfer rates on both sides of the transfer.

* Your free usage is calculated each month across all regions and automatically applied to your bill – free usage does not accumulate.
** As part of AWS’s Free Usage Tier, new AWS customers will receive free 15 GB of data transfer out each month aggregated across all AWS services for one year.
*** Data transfer out rate tiers aggregate outbound data transfer across Amazon EC2, Amazon EBS, Amazon S3, Amazon Glacier, Amazon RDS, Amazon SimpleDB, Amazon SQS, Amazon SNS, Amazon DynamoDB, AWS Storage Gateway, and Amazon VPC. US East (N. Virginia) US West (Northern California) US West (Oregon) EU (Ireland) Asia Pacific (Singapore) Asia Pacific (Tokyo) Asia Pacific (Sydney) South America (Sao Paulo) US West (Northern California) EU (Ireland) Asia Pacific (Singapore) Asia Pacific (Tokyo) Asia Pacific (Sydney) per Hour Red Hat Enterprise Linux per GB Currency Region Windows with SQL Standard Usage Windows with SQL Web Usage All data transfer in All data transfer in Cluster Compute Reserved Instances Cluster Compute Instances Cluster GPU Instances Cluster GPU Reserved Instances High-Memory Cluster On-Demand Instances High-Memory Cluster Reserved Instances High-Memory Cluster Spot Instances Some instance types may not be available in your region. Some instance types may not be available in your region. Data Transfer** Data Transfer IN Data Transfer OUT Data Transfer IN To Amazon EC2 From Data Transfer OUT From Amazon EC2 To Data Transfer OUT From Amazon EC2 To Internet Internet Another AWS Region (from any AWS Service) Amazon S3, Amazon Glacier, Amazon DynamoDB, Amazon SQS, or Amazon SimpleDB in the same AWS Region     Using a private IP address     Using a public or Elastic IP address Amazon EC2, Amazon RDS and Amazon ElastiCache instances or Elastic Network Interfaces in another Availability Zone in the same AWS Region Amazon S3, Amazon Glacier, Amazon DynamoDB, Amazon SQS, Amazon SimpleDB in the same AWS Region     Using a private IP address     Using a public or Elastic IP address Amazon EC2, Amazon RDS or Amazon ElastiCache instances, Amazon Elastic Load Balancing, or Elastic Network Interfaces in another Availability Zone in the same AWS Region Another AWS Region or Amazon CloudFront Amazon EC2, Amazon RDS and Amazon ElastiCache instances or Elastic Network Interfaces in the same Availability Zone Amazon EC2, Amazon RDS, or Amazon ElastiCache instances, Amazon Elastic Load Balancing, or Elastic Network Interfaces in the same Availability Zone Amazon EBS Snapshots to Amazon S3 Amazon EBS Provisioned IOPS volumes Amazon EBS Standard volumes EBS-Optimized Usage First 1 GB / month High-CPU Instances High-CPU On-Demand Instances High-CPU Reserved Instances High-CPU Spot Instances High-Memory Instances High-Memory On-Demand Instances High-Memory Reserved Instances High-Memory Spot Instances High-I/O On-Demand Instances High-I/O Reserved Instances High-I/O Spot Instances High-Storage On-Demand Instances High-Storage Reserved Instances High-Storage Spot Instances Second Generation Standard Instances Second Generation Standard On-Demand Instances Second Generation Standard Reserved Instances Second Generation Standard Spot Instances Second Generation Standard Storage Large Linux/UNIX Usage Medium Medium Windows Usage Next 350 TB / month Next 524 TB / month Next 4 PB / month Greater than 5 PB / month Over 5 PB / month Next 100 TB / month Next 10 TB / month Next 40 TB / month Windows® is not currently available for Cluster Compute or Cluster GPU Instances Greater than 150 TB / month per 10,000 GET requests (when loading a snapshot) per 1,000 PUT requests (when saving a snapshot) per GB in/out per GB-month of data stored per GB-month of provisioned storage per 1 million I/O requests per provisioned IOPS-month per hour Pricing PUT, COPY, POST, or LIST Requests Reduced Redundancy Storage Small (Default) Standard Instances Standard On-Demand Instances Standard Reserved Instances Standard Spot Instances Standard Storage Micro Micro On-Demand Instances Micro Reserved Instances Micro Spot Instances Up to 10 TB / month Extra Large Double Extra Large Quadruple Extra Large Eight Extra Large 1 yr Term 3 yr Term Upfront Hourly for one Elastic IP address associated with a running instance per additional Elastic IP address associated with a running instance per hour on a pro rata basis per Elastic IP address not associated with a running instance per hour on a pro rata basis per Elastic IP address remap for the first 100 remaps per month per Elastic IP address remap for additional remaps over 100 per month Detailed Monitoring for Amazon EC2 Instances per instance-hour (or partial hour) for Detailed Monitoring at 1-minute frequency per instance per month, provided at 1-minute frequency Basic Monitoring for Amazon EC2 instances (free of charge) per instance per month, provided at 5-minute frequency Monitoring for Custom Metrics per metric per month per Elastic Load Balancer-hour (or partial hour) per GB of data processed by an Elastic Load Balancer Eight Extra Large

---

Resources

---

Detailed Description

Working with Amazon SQS

Amazon SQS can be easily accessed through the AWS Management Console, which gives users a point-and-click, web-based interface to setup and manage Amazon SQS.

Basic Queue Requests

Amazon SQS employs a simple interface that is easy to use and highly flexible. The following requests are provided:

• CreateQueue: Create queues for use with your AWS account.
• ListQueues: List your existing queues.
• DeleteQueue: Delete one of your queues.
• SendMessage: Add messages to a specified queue.
• SendMessageBatch: Add multiple messages to a specified queue.
• ReceiveMessage: Return one or more messages from a specified queue.
• ChangeMessageVisibility: Change the visibility timeout of previously received message.
• ChangeMessageVisibilityBatch: Change the visibility timeout of multiple previously received messages.
• DeleteMessage: Remove a previously received message from a specified queue.
• DeleteMessageBatch: Remove multiple previously received messages from a specified queue.
• SetQueueAttributes: Control queue settings like the amount of time that messages are locked after being read so they cannot be read again.
• GetQueueAttributes: Get information about a queue like the number of messages in it.
• GetQueueUrl: Get the queue URL.
• AddPermission: Add queue sharing for another AWS account for a specified queue.
• RemovePermission: Remove an AWS account from queue sharing for a specified queue.

Amazon SQS Message Lifecycle

Messages that are stored in Amazon SQS have a lifecycle that is easy to manage but ensures that all messages are processed.

1. A system that needs to send a message will find an Amazon SQS queue, and use SendMessage to add a new message to it.
2. A different system that processes messages needs more messages to process, so it calls ReceiveMessage, and this message is returned.
3. Once a message has been returned by ReceiveMessage, it will not be returned by any other ReceiveMessage until the visibility timeout has passed. This keeps multiple computers from processing the same message at once.
4. If the system that processes messages successfully finishes working with this message, it calls DeleteMessage, which removes the message from the queue so no one else will ever process it. If this system fails to process the message, then it will be read by another ReceiveMessage call as soon as the visibility timeout passes.

---

Intended Usage and Restrictions

Your use of this service is subject to the Amazon Web Services Customer Agreement