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
I use AWS in my project.
I have a use case where that is not important to me to persist the messages from more than 1 hour.
So for me just SNS push notification is ok. I publish to the topic, SNS send me the push notification with the message, if response is 200 it ends there, if there is some error, SNS will keep trying some more to deliver the message based on my configuration for 'notification_retries'.
Could you implement a configuration parameter like 'push_notification_only' or 'push_notification_no_queue' to us?
Thank you!
The text was updated successfully, but these errors were encountered:
With this i have tried to implement a configuration parameter that allow me to use the bundle and aws provider only with the SNS to push messages to my backend, without SQS.
I know that SNS have the maximum retention time of 1 hour for messages but this is ok for my use case.
I also want to make the bundle able to configure/atach a delivery policy to be able to configure 'notification_retries' and 'retry_timeout' but until now i do not know how to do it.
If someone can help would be nice. Until i am able to do this, ill manually configure the delivery policy in SNS dashboard.
Please let me now if you find some problem with my changes.
Hey guys,
I use AWS in my project.
I have a use case where that is not important to me to persist the messages from more than 1 hour.
So for me just SNS push notification is ok. I publish to the topic, SNS send me the push notification with the message, if response is 200 it ends there, if there is some error, SNS will keep trying some more to deliver the message based on my configuration for 'notification_retries'.
Could you implement a configuration parameter like 'push_notification_only' or 'push_notification_no_queue' to us?
Thank you!
The text was updated successfully, but these errors were encountered: