InvalidParameterValue cloud config_error ai_generated true

InvalidParameterValue：队列 'my-queue' 的重驱策略无效。原因：死信队列 ARN 无效。

InvalidParameterValue: The redrive policy for queue 'my-queue' is invalid. Reason: The dead-letter queue ARN is not valid.

ID: cloud/aws-sqs-redrive-policy-invalid

其他格式: JSON · Markdown 中文 · English
88%修复率
84%置信度
1证据数
2024-12-01首次发现

版本兼容性

版本状态引入弃用备注
AWS SDK for Python (boto3): 1.34.0 active — — —
SQS: 2012-11-05 active — — —
Terraform AWS Provider: 5.70.0 active — — —

根因分析

重驱策略中指定的死信队列 ARN 不存在、位于不同区域，或者源队列没有向其发送消息的权限。

English

The dead-letter queue ARN specified in the redrive policy does not exist, is in a different region, or the source queue does not have permission to send messages to it.

generic

官方文档

https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html

解决方案

  1. 使用 AWS CLI 验证死信队列 ARN：aws sqs get-queue-attributes --queue-url <DLQ_URL> --attribute-names QueueArn。然后使用正确的 ARN 更新重驱策略。
  2. 向死信队列附加基于资源的策略，允许源队列发送消息：aws sqs set-queue-attributes --queue-url <DLQ_URL> --attributes Policy='{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Principal":"*","Action":"sqs:SendMessage","Resource":"<DLQ_ARN>","Condition":{"ArnEquals":{"aws:SourceArn":"<SOURCE_ARN>"}}}]}'
  3. 确保两个队列位于同一 AWS 区域；如果不在，则在源队列所在区域创建新的死信队列。

无效尝试

常见但无效的做法:

  1. 80% 失败

    Recreating queues does not fix the ARN mismatch or permission issue; the new queues have different ARNs unless explicitly specified.

  2. 90% 失败

    This only delays the problem; messages still get stuck in the source queue if processing fails repeatedly, and the redrive policy remains invalid.

  3. 95% 失败

    The redrive policy requires an ARN, not a URL; using a URL causes the same invalid parameter error.