Serverless AWS Lambda Development · Lesson

Dead Letter Queues (DLQ) for Failures

Configure Dead Letter Queues (DLQ) with SQS or SNS to capture and handle failed asynchronous Lambda invocations, improving system resilience and debugging.

Dead Letter Queues (DLQ) for Failures is a free Serverless AWS Lambda Development lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Serverless AWS Lambda Development learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Why Dead Letter Queues?

When building serverless applications, especially with asynchronous Lambda functions, what happens if an invocation fails repeatedly?

Without a proper mechanism, these failed events might simply be discarded, leading to data loss or unaddressed issues. This is where Dead Letter Queues (DLQs) come in.

Async Lambda Invocation Review

First, let's quickly recap how asynchronous Lambda invocations work. When you invoke a Lambda function asynchronously (e.g., via S3, SNS, or direct API call with InvocationType: Event):

Lambda places the event in an internal queue.
It then attempts to invoke your function.
If the function fails, Lambda automatically retries the invocation up to two times.

Unhandled Async Failures

What happens if your Lambda function still fails after all automatic retries (initial attempt + two retries)?

By default, if no DLQ is configured, the event is simply discarded. This means you lose valuable information about what went wrong and the event data itself, making debugging and error recovery difficult.

Dead Letter Queue Defined

A Dead Letter Queue (DLQ) is a destination for events that Lambda couldn't successfully process after exhausting all retry attempts.

Think of it as a 'parking lot' for problematic messages. Instead of disappearing, these failed events are sent to your chosen DLQ destination, allowing you to inspect, debug, and potentially re-process them later.

DLQ Destinations: SQS or SNS?

You can configure two types of AWS services as DLQ destinations for your Lambda functions:

Amazon SQS (Simple Queue Service): A message queue. Failed events are sent to the SQS queue, where they await processing. This is a pull-based model.
Amazon SNS (Simple Notification Service): A topic. Failed events are published to an SNS topic, which can then notify subscribers (e.g., email, other Lambda functions). This is a push-based model.

SQS is generally preferred for re-processing, while SNS is good for immediate notifications.

Configuring an SQS DLQ

To use an SQS queue as a DLQ, you first need to create one. It's a standard SQS queue, but often named to indicate its purpose (e.g., my-lambda-dlq).

Here's how you might create a standard SQS queue using the AWS CLI:

aws sqs create-queue \
  --queue-name my-lambda-dlq

Connect Lambda to DLQ

Once your SQS queue is ready, you configure your Lambda function to use it as its DLQ. This involves updating the function's configuration.

You also need to ensure your Lambda's IAM execution role has permissions to send messages to the SQS queue (sqs:SendMessage).

aws lambda update-function-configuration \
  --function-name MyFailingLambda \
  --dead-letter-config TargetArn=arn:aws:sqs:REGION:ACCOUNT_ID:my-lambda-dlq

Demo: Lambda Failure to DLQ

Consider this Python Lambda function. It processes an event, but if the event contains "should_fail": true, it will raise an exception.

When invoked asynchronously, after retries, an event causing this failure would be sent to the configured DLQ.

def lambda_handler(event, context):
    print(f"Processing event: {event}")
    # Simulate an error condition
    if event.get("should_fail", False):
        raise Exception("Simulated processing error!")
    return {
        'statusCode': 200,
        'body': 'Processed successfully!'
    }

# This part makes it runnable outside Lambda for demonstration
if __name__ == "__main__":
    print("--- Simulating a successful invocation ---")
    result_success = lambda_handler({"key": "value"}, None)
    print(f"Success Result: {result_success}\n")

    print("--- Simulating a failed invocation ---")
    try:
        result_fail = lambda_handler({"should_fail": True}, None)
        print(f"Failure Result: {result_fail}")
    except Exception as e:
        print(f"Caught expected error: {e}")
        print("This event would eventually go to a DLQ after retries.")

Managing Failed Events

Once events are in your DLQ, you can:

Monitor: Use Amazon CloudWatch to track the number of messages in the DLQ.
Inspect: View the content of the messages to understand the failure.
Re-process: Move messages back to the original queue or trigger manual processing once the underlying issue is resolved.

This provides a crucial safety net for your asynchronous workflows.

DLQ Quick Check

You've learned about Dead Letter Queues and their importance. Let's test your understanding!

Recap: DLQs for Resilience

In this lesson, we explored Dead Letter Queues (DLQs) and their role in building resilient serverless applications. You learned:

DLQs prevent data loss from failed asynchronous Lambda invocations.
AWS SQS and SNS can serve as DLQ destinations.
How to configure a Lambda function with a DLQ.
The importance of monitoring and managing events in your DLQ.

DLQs are essential for robust error handling in event-driven architectures.

Frequently asked questions

Is the “Dead Letter Queues (DLQ) for Failures” lesson free?

Yes — the full text of “Dead Letter Queues (DLQ) for Failures” is free to read here on the web, and the Serverless AWS Lambda Development course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Serverless AWS Lambda Development course, upgrade to CoddyKit PRO.

What will I learn in “Dead Letter Queues (DLQ) for Failures”?

Configure Dead Letter Queues (DLQ) with SQS or SNS to capture and handle failed asynchronous Lambda invocations, improving system resilience and debugging. You practise Serverless AWS Lambda Development with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Serverless AWS Lambda Development?

No prior experience is required. Serverless AWS Lambda Development on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Dead Letter Queues (DLQ) for Failures” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Serverless AWS Lambda Development lesson?

Yes. Every Serverless AWS Lambda Development lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Serverless AWS Lambda Development