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.
Is task delivery exactly once as in a SQS FIFO queue?asked 5 years ago
SQS FIFO with JMS fail to add message group IDasked 5 years ago
SQS not receiving SNS messageasked 3 years ago
Textract using FIFO SNS topics and FIFO SQS queuesasked a year ago
How can I delete a "hidden" SQSasked 7 months ago
SES Status Notification with SQS FIFO Queueasked 4 months ago
List queue messages yet unprocessed by consumerasked 7 months ago
Multiple SQS queue to same Lambdaasked 6 months ago
Integrating KMS keys with SQS queries, cloudformation being used to deploy resourcesasked 7 months ago
How to remove emails from AWS SES queueasked 2 months ago