SQS queue concept in AWS - Mini Project: Build & Apply

Create and Configure an AWS SQS Queue

📖 Scenario: You are setting up a simple messaging system in AWS to decouple parts of an application. You will create an SQS queue, configure its visibility timeout, and enable dead-letter queue support.

🎯 Goal: Build an AWS CloudFormation template that creates an SQS queue named MyQueue, sets its visibility timeout to 30 seconds, and configures a dead-letter queue named MyDeadLetterQueue with a max receive count of 5.

📋 What You'll Learn

Create an SQS queue named MyQueue

Create a dead-letter SQS queue named MyDeadLetterQueue

Set the visibility timeout of MyQueue to 30 seconds

Configure MyQueue to use MyDeadLetterQueue as its dead-letter queue with a max receive count of 5

💡 Why This Matters

🌍 Real World

SQS queues are used to decouple microservices and handle asynchronous message processing reliably.

💼 Career

Cloud engineers and DevOps professionals often create and configure SQS queues to build scalable, fault-tolerant systems.

1

Create the main SQS queue resource

Create an AWS CloudFormation resource named MyQueue of type AWS::SQS::Queue with no properties yet.

AWS

# Your code here to create the MyQueue resource

Hint

Use the Resources section and define MyQueue with the correct type.

2

Create the dead-letter queue resource

Add an AWS CloudFormation resource named MyDeadLetterQueue of type AWS::SQS::Queue below MyQueue.

AWS

Resources:
  MyQueue:
    Type: AWS::SQS::Queue
  # Your code here to create MyDeadLetterQueue resource

Hint

Define MyDeadLetterQueue as another SQS queue resource.

3

Set visibility timeout for MyQueue

Add a Properties section to MyQueue and set VisibilityTimeout to 30 seconds.

AWS

Resources:
  MyQueue:
    Type: AWS::SQS::Queue
    # Your code here to add Properties with VisibilityTimeout 30
  MyDeadLetterQueue:
    Type: AWS::SQS::Queue

Hint

Use the Properties key under MyQueue to set the timeout.

4

Configure dead-letter queue for MyQueue

Add a RedrivePolicy property under MyQueue Properties that references MyDeadLetterQueue ARN and sets maxReceiveCount to 5.

AWS

Resources:
  MyQueue:
    Type: AWS::SQS::Queue
    Properties:
      VisibilityTimeout: 30
      # Your code here to add RedrivePolicy
  MyDeadLetterQueue:
    Type: AWS::SQS::Queue

Hint

Use !GetAtt MyDeadLetterQueue.Arn to get the ARN of the dead-letter queue.

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