SQS queue concept in AWS - Commands & Configuration

Introduction

Sometimes apps need to talk to each other without waiting. SQS queues help by holding messages safely until the other app is ready to read them.

When you want to send orders from a website to a warehouse system without slowing down the website.

When you need to process tasks one by one in the background, like resizing images uploaded by users.

When different parts of your app run on separate servers and need to share information reliably.

When you want to handle sudden bursts of messages without losing any.

When you want to make sure messages are not lost even if one part of your system is down.

Commands

This command creates a new SQS queue named 'my-app-queue' where messages can be stored and retrieved.

Terminal

aws sqs create-queue --queue-name my-app-queue

Expected Output

{"QueueUrl": "https://sqs.us-east-1.amazonaws.com/123456789012/my-app-queue"}

→

--queue-name - Specifies the name of the queue to create

This command lists all the SQS queues in your AWS account to confirm the queue was created.

Terminal

aws sqs list-queues

Expected Output

{"QueueUrls": ["https://sqs.us-east-1.amazonaws.com/123456789012/my-app-queue"]}

This command sends a message with the text 'Hello from my app' to the queue so it can be processed later.

Terminal

aws sqs send-message --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/my-app-queue --message-body "Hello from my app"

Expected Output

{"MD5OfMessageBody": "8b1a9953c4611296a827abf8c47804d7", "MessageId": "1234abcd-56ef-78gh-90ij-klmnopqrstuv"}

→

--queue-url - Specifies the exact queue to send the message to

→

--message-body - The content of the message being sent

This command retrieves one message from the queue so your app can read and process it.

Terminal

aws sqs receive-message --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/my-app-queue

Expected Output

{"Messages": [{"MessageId": "1234abcd-56ef-78gh-90ij-klmnopqrstuv", "ReceiptHandle": "AQEB1234...", "MD5OfBody": "8b1a9953c4611296a827abf8c47804d7", "Body": "Hello from my app"}]}

→

--queue-url - Specifies the queue to receive messages from

This command deletes the message from the queue after it has been processed to avoid processing it again.

Terminal

aws sqs delete-message --queue-url https://sqs.us-east-1.amazonaws.com/123456789012/my-app-queue --receipt-handle AQEB1234...

Expected Output

No output (command runs silently)

→

--queue-url - Specifies the queue where the message is located

→

--receipt-handle - Unique identifier for the message to delete

Key Concept

If you remember nothing else from this pattern, remember: SQS queues hold messages safely so apps can work at their own pace without losing data.

Common Mistakes

Trying to receive messages from the queue without specifying the correct queue URL.

The command will fail or return no messages because it doesn't know which queue to check.

Always include the exact queue URL with --queue-url when receiving or deleting messages.

Not deleting messages after processing them.

Messages stay in the queue and can be processed multiple times, causing duplicate work.

Use the delete-message command with the receipt handle after processing each message.

Using the queue name instead of the queue URL in commands that require the URL.

AWS CLI commands expect the full queue URL, not just the name, so the command will fail.

Use the queue URL returned when creating or listing queues for commands that need it.

Summary

Create an SQS queue with aws sqs create-queue to hold messages.

Send messages to the queue using aws sqs send-message with the queue URL.

Receive messages with aws sqs receive-message and process them.

Delete messages after processing with aws sqs delete-message to prevent duplicates.

Practice

1. What is the main purpose of an AWS SQS queue?

easy

A. To store messages safely between different parts of a system

B. To run code automatically when triggered

C. To host websites and web applications

D. To store large files like videos and images

Solution

1. Step 1: Understand what SQS does

   AWS SQS is designed to hold messages so different parts of a system can communicate safely without losing data.

2. Step 2: Compare options with SQS purpose

   Running code automatically is Lambda's job, hosting websites is for services like S3 or EC2, and storing large files is for S3. Only storing messages fits SQS.

3. Final Answer:

   To store messages safely between different parts of a system -> Option A

4. Quick Check:

   SQS = message storage between system parts [OK]

Hint: SQS holds messages, not code or files [OK]

Common Mistakes:

• Confusing SQS with Lambda or S3
• Thinking SQS runs code
• Assuming SQS stores large files

2. Which of the following is the correct way to create a standard SQS queue using AWS CLI?

easy

A. aws sqs create-queue --queue-name MyQueue --attributes DelaySeconds=0

B. aws sqs create-queue MyQueue --delay 0

C. aws sqs new-queue --name MyQueue

D. aws sqs make-queue --queue MyQueue --delay 0

Solution

1. Step 1: Recall AWS CLI syntax for creating SQS queue

   The correct command uses 'aws sqs create-queue' with '--queue-name' and optional '--attributes'.

2. Step 2: Check each option's syntax

   aws sqs create-queue --queue-name MyQueue --attributes DelaySeconds=0 matches the correct syntax. Options B, C, and D use incorrect commands or flags.

3. Final Answer:

   aws sqs create-queue --queue-name MyQueue --attributes DelaySeconds=0 -> Option A

4. Quick Check:

   Correct CLI syntax = aws sqs create-queue --queue-name MyQueue --attributes DelaySeconds=0 [OK]

Hint: Use 'aws sqs create-queue --queue-name' to create queues [OK]

Common Mistakes:

• Using wrong command verbs like 'new-queue' or 'make-queue'
• Missing '--queue-name' flag
• Incorrect attribute syntax

3. Given this code snippet using AWS SDK to receive messages from an SQS queue, what will be the output if the queue is empty?

const params = { QueueUrl: 'https://sqs.us-east-1.amazonaws.com/123456789012/MyQueue', MaxNumberOfMessages: 1 };
const data = await sqs.receiveMessage(params).promise();
console.log(data.Messages);

medium

A. []

B. null

C. undefined

D. An error is thrown

Solution

1. Step 1: Understand SQS receiveMessage behavior when empty

   If no messages are available, the 'Messages' property is not included in the response, so data.Messages is undefined.

2. Step 2: Check what console.log prints

   Logging undefined prints 'undefined' in JavaScript, not null or empty array. No error is thrown.

3. Final Answer:

   undefined -> Option C

4. Quick Check:

   Empty queue means data.Messages = undefined [OK]

Hint: Empty queue returns undefined Messages, not empty array [OK]

Common Mistakes:

• Assuming empty array is returned
• Expecting null instead of undefined
• Thinking an error occurs on empty queue

4. You set the VisibilityTimeout of an SQS queue to 30 seconds. A message is received and not deleted. What happens after 30 seconds?

medium

A. The message is deleted automatically

B. The message becomes visible again and can be received again

C. The message is moved to a dead-letter queue

D. The queue stops delivering messages

Solution

1. Step 1: Understand VisibilityTimeout effect

   VisibilityTimeout hides a message from other consumers for the set time after being received.

2. Step 2: What happens if message is not deleted after timeout?

   If not deleted, after 30 seconds the message becomes visible again for processing by others.

3. Final Answer:

   The message becomes visible again and can be received again -> Option B

4. Quick Check:

   VisibilityTimeout expiry = message visible again [OK]

Hint: VisibilityTimeout hides message temporarily, then shows it again [OK]

Common Mistakes:

• Thinking message deletes automatically after timeout
• Confusing dead-letter queue behavior
• Assuming queue stops working

5. You want to delay processing of messages by 10 minutes after they are sent to an SQS queue. Which configuration should you use?

hard

A. Set the VisibilityTimeout to 600 seconds

B. Set the ReceiveMessageWaitTimeSeconds to 600 seconds

C. Set the MessageRetentionPeriod to 600 seconds

D. Set the DelaySeconds attribute to 600 on the queue or per message

Solution

1. Step 1: Identify delay setting for message delivery

   DelaySeconds controls how long a message waits before becoming visible after sending.

2. Step 2: Compare other attributes

   VisibilityTimeout controls message invisibility after receipt, MessageRetentionPeriod controls how long messages stay in queue, ReceiveMessageWaitTimeSeconds controls long polling wait time.

3. Final Answer:

   Set the DelaySeconds attribute to 600 on the queue or per message -> Option D

4. Quick Check:

   DelaySeconds = message delivery delay [OK]

Hint: Use DelaySeconds to delay message visibility after sending [OK]

Common Mistakes:

• Confusing VisibilityTimeout with DelaySeconds
• Using MessageRetentionPeriod for delay
• Mistaking ReceiveMessageWaitTimeSeconds for delay