SQS queue concept in AWS - Step-by-Step Execution

Process Flow - SQS queue concept

Message sent by Producer

↓

Message stored in SQS Queue

↓

Message waits in queue until consumed

↓

Consumer polls queue

↓

Message received and processed

↓

Message deleted from queue

↓

End

Messages are sent by producers to the queue, stored until consumers poll and process them, then deleted after processing.

Execution Sample

AWS

SendMessage -> Queue stores message -> ReceiveMessage -> Process -> DeleteMessage

Shows the basic flow of sending, receiving, processing, and deleting a message in SQS.

Process Table

Step	Action	Queue State	Message Visibility	Result
1	Producer sends message	1 message added	Visible	Message stored in queue
2	Consumer polls queue	1 message in queue	Invisible	Message received by consumer
3	Consumer processes message	1 message invisible	Invisible	Processing in progress
4	Consumer deletes message	0 messages	N/A	Message removed from queue
5	Consumer polls again	0 messages	N/A	No messages to receive

💡 Queue empty, no messages left to process

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Queue Message Count	0	1	1	1	0	0
Message Visibility	N/A	Visible	Invisible	Invisible	N/A	N/A

Key Moments - 3 Insights

Why does the message become invisible after the consumer polls it?

When the consumer polls the message (Step 2), it becomes invisible to other consumers to prevent duplicate processing, as shown in the execution_table row 2.

What happens if the consumer does not delete the message after processing?

If the message is not deleted, it becomes visible again after the visibility timeout, allowing other consumers to receive it, which can cause duplicate processing. This is implied between Steps 3 and 5.

Why does the queue message count remain 1 during processing?

The message stays in the queue until deleted, so during processing (Step 3), the count is still 1 but the message is invisible, as shown in the variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table at Step 2, what is the message visibility state?

A Deleted

B Visible

C Invisible

D Not in queue

💡 Hint

Check the 'Message Visibility' column at Step 2 in the execution_table.

At which step does the queue become empty?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Look at the 'Queue State' column in the execution_table to find when message count is zero.

If the consumer never deletes the message, what would happen at Step 5?

A Message would become visible again

B Queue would be empty

C Message would still be invisible

D Message would be deleted automatically

💡 Hint

Refer to the key_moments explanation about message visibility timeout and deletion.

Concept Snapshot

SQS queue stores messages sent by producers.
Consumers poll messages, which become invisible during processing.
After processing, consumers delete messages to remove them.
If not deleted, messages reappear after visibility timeout.
This ensures reliable, at-least-once delivery.

Full Transcript

Amazon SQS is a message queue service where producers send messages that are stored until consumers poll them. When a consumer receives a message, it becomes invisible to others to avoid duplicate processing. The consumer processes the message and then deletes it from the queue. If the message is not deleted, it becomes visible again after a timeout, allowing reprocessing. This flow ensures messages are reliably delivered and processed.

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