- Newest
- Most votes
- Most comments
Hi,
Thanks for reaching out. I would like to echo Eduardo's thoughts here and would like to confirm your use case and how exactly you are sending the SES notifications to the SQS FIFO queue at the moment?
Currently, we can only send SES notifications to a standard SNS topic so I am curious how you are sending this to an SQS FIFO queue. The MessageGroupID is a parameter that we need to set when sending messages to the SQS FIFO queue(unless the message comes from an SNS FIFO Queue). if you are sending messages to an SQS FIFO queue, then you are already somehow setting the MessageGroupID somewhere as this is a required parameter for SQS FIFO queues.
Important
MessageGroupId is required for FIFO queues. You can't use it for Standard queues.
So it seems there is some context and information that we are missing. Kindly share some additional details and we will do our best to help you.
Hi, thanks for your question. As mentioned by Ryan, SES can send notifications to SNS. I suggest you take a look at this reference architecture and accompanying CloudFormation template to deploy this architecture: https://github.com/aws-samples/communication-developer-services-reference-architectures#SES-Event-Processing
Best.
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
Could you describe a little bit more about your architecture? I think you are using the SES notifications to send the notifications to a SNS topic, and from there, to a SQS queue. In this architecture, SES doesn't support SNS FIFO, and SNS standard doesn't send the messages to SQS FIFO. I'd like to know how are you sending the notifications to a SQS FIFO and why you need to keep the order of the messages.