-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(aws-events-targets): Using an imported DLQ with an event rule target throws Error: Cannot assign Dead Letter Queue in region ${Token[TOKEN.35]} to the rule XYZEventRule89558AAC in region eu-west-1. Both the queue and the rule must be in the same region.
#28165
Comments
Is the error message from cloudformation? Looks like the region of the failedEventQueue can't be resolved. const failedEventQueue = sqs.Queue.fromQueueArn(
this,
"FailedEventsQueue",
ssm.StringParameter.valueForStringParameter(
this,
`xyz/failed-events-queue-arn`
)
); Can you assign a static ARN to And, can you confirm if the value is successfully retrieved from the given parameter? |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
I am having the same issue, I have checked that the Rule and Dead Letter Queue are in the same region but I can't resolve this. |
I can confirm that after reverting back to CDK version 2.93.0, it works. Looks like this is a bug with latest version. |
I also encountered the same problem. The region settings are fine and they are set in Node.js: v20.9.0 |
Sorry for the delay, : I tried with issue still exists in 2.114.1 |
With #27906 PR, the region/account is now considered as resolved and are not anymore tokens. As a workaround, I suggest changing
to
|
Looks like a [small] regression we've introduced, so labeling this p0. It isn't going to matter much in terms of priority, as @JeromeGuyon has already created a fix that has been accepted (thanks :)). |
…28165) (#28285) This PR fixes the bug where imported SQS queue cannot be used as Rule DeadLetterQueue, since fromQueueArn can resolve region and account from v2.109.0 Closes #28165 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Error: Cannot assign Dead Letter Queue in region
Error: Cannot assign Dead Letter Queue in region
Error: Cannot assign Dead Letter Queue in region...Both the queue and the rule must be in the same region.
Error: Cannot assign Dead Letter Queue in region...Both the queue and the rule must be in the same region.
Error: Cannot assign Dead Letter Queue in region ${Token[TOKEN.35]} to the rule XYZEventRule89558AAC in region eu-west-1. Both the queue and the rule must be in the same region.
…ws#28165) (aws#28285) This PR fixes the bug where imported SQS queue cannot be used as Rule DeadLetterQueue, since fromQueueArn can resolve region and account from v2.109.0 Closes aws#28165 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Please add your +1 👍 to let us know you have encountered this
Status: RESOLVED
Overview:
All users of
aws-events-targets
who created aRule
with theSqsQueue
target and passed an imported queue to thedeadLetterQueue
prop would receive an error similar to:Complete Error Message:
Workaround:
Solution:
Upgrade to 2.116.0 or higher.
Related Issues:
Original report
Describe the bug
Previously (2.95.1), I was able to associate a DLQ to a Rule.
In last version (2.111.0), it is nor more possible :
Generate
Expected Behavior
It should be possible to support imported SQS Queue as DLQ.
Current Behavior
Reproduction Steps
and in stack
env: { account: process.env.CDK_DEFAULT_ACCOUNT, region: process.env.CDK_DEFAULT_REGION },
Possible Solution
N/A
Additional Information/Context
No response
CDK CLI Version
2.108.0
Framework Version
No response
Node.js Version
v18.13.0
OS
macos
Language
TypeScript
Language Version
TypeScript (5.2.2)
Other information
No response
The text was updated successfully, but these errors were encountered: