Amazon Simple Queue Service (SQS) is a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications. SQS eliminates the complexity and overhead associated with managing and operating message-oriented middleware, and empowers developers to focus on differentiating work.
When working with AWS SQS, you might encounter the error code AWS.SimpleQueueService.InvalidRedrivePolicy. This error typically arises when there is an issue with the redrive policy configuration of your SQS queue.
Developers may notice that messages are not being moved to the dead-letter queue (DLQ) as expected, or they might receive an error message indicating an invalid redrive policy when attempting to configure or update a queue.
The AWS.SimpleQueueService.InvalidRedrivePolicy error indicates that the redrive policy attached to your SQS queue is not correctly formatted or references a non-existent DLQ. A redrive policy specifies the conditions under which messages are moved from the source queue to a DLQ after they fail to be processed successfully.
To resolve the AWS.SimpleQueueService.InvalidRedrivePolicy error, follow these steps:
Ensure that the DLQ specified in your redrive policy exists and is correctly configured. You can list your queues and verify the ARN using the AWS CLI:
aws sqs list-queues
Check the ARN of the DLQ and ensure it matches the one in your redrive policy.
Ensure that your redrive policy JSON is correctly formatted. A typical redrive policy looks like this:
{
"deadLetterTargetArn": "arn:aws:sqs:region:account-id:DLQ-name",
"maxReceiveCount": "5"
}
Use a JSON validator to check for syntax errors.
If you find any issues, update the redrive policy using the AWS Management Console or AWS CLI:
aws sqs set-queue-attributes --queue-url https://sqs.region.amazonaws.com/account-id/queue-name --attributes RedrivePolicy='{"deadLetterTargetArn":"arn:aws:sqs:region:account-id:DLQ-name","maxReceiveCount":"5"}'
For more information on configuring redrive policies, refer to the AWS SQS Dead-Letter Queues Documentation. For troubleshooting common SQS issues, visit the AWS Knowledge Center.
(Perfect for DevOps & SREs)
(Perfect for DevOps & SREs)



