You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#854 makes it easy to build SNS->SQS->Lambda configurations.
When I looked at the documentation, it was not clear whether the RedrivePolicy was for SNS or SQS.
From the actual behavior, I can guess that this seems to be a RedrivePolicy for SNS.
The failure of the SNS->SQS integration does not need to be taken into account by the average user, and in fact, a Redrive due to an error in the SQS->Lambda integration is required.
Perhaps adding a new key like SqsRedrivePolicy or instructing SAM to automatically create the required SQS when specifying an object in SqsSubscription, like the traditional true, would fulfill the requirement.
Option1: Adding SqsRedrivePolicy
Type: SNSProperties:
Topic: arn:aws:sns:us-east-1:123456789012:my_topicSqsSubscription: trueRedrivePolicy:
deadLetterTargetArn: !GetAtt QueueSNSDlq.ArnSqsRedrivePolicy: # <----- New key for SQS redrive policydeadLetterTargetArn: !GetAtt QueueFunctionDlq.ArnmaxReceiveCount: 1
Using this option requires validation of the reciprocal relationship that SqsSubscription must be specified when using SqsRedrivePolicy.
Option2: Support RedrivePolicy on SqsSubscriptionObject
Hello @conao3
If you need to have custom properties (i.e. RedrivePolicy, VisibilityTimeout, etc) set on the SNS->SQS->Lambda generated AWS::SQS::Queue please define a custom SQS Queue. Then in the 'SNS' Event on the AWS::Serverless::Function reference the AWS::SQS::Queue in the SqsSubscription: like below. Please respond if you have any questions, or if this does not work for what you are trying to do.
#854 makes it easy to build SNS->SQS->Lambda configurations.
When I looked at the documentation, it was not clear whether the RedrivePolicy was for SNS or SQS.
From the actual behavior, I can guess that this seems to be a RedrivePolicy for SNS.
The failure of the SNS->SQS integration does not need to be taken into account by the average user, and in fact, a Redrive due to an error in the SQS->Lambda integration is required.
Perhaps adding a new key like SqsRedrivePolicy or instructing SAM to automatically create the required SQS when specifying an object in SqsSubscription, like the traditional true, would fulfill the requirement.
Option1: Adding
SqsRedrivePolicy
Using this option requires validation of the reciprocal relationship that
SqsSubscription
must be specified when usingSqsRedrivePolicy
.Option2: Support
RedrivePolicy
onSqsSubscriptionObject
Using this option requires the SQS to be explicitly created by the user.
(This is a potential issue to be resolved by a separate feature request).
The text was updated successfully, but these errors were encountered: