Service
SQS
API Action / Feature
SendMessage — MessageGroupId parameter on standard (non-FIFO) queues
AWS Documentation
SendMessage — MessageGroupId parameter on standard (non-FIFO) queues
ReceiveMessage — MessageGroupId system attribute
Why is this needed?
Our application sends messages to standard (non-FIFO) SQS queues using the AWS SDK's SendMessageRequest with MessageGroupId set to a caller-supplied correlation value (an EnvironmentId GUID):
SendMessageRequest sqsSendMessageRequest = new()
{
QueueUrl = myQueueUrl,
MessageBody = JsonSerializer.Serialize(message),
MessageGroupId = myQueueUrl.EndsWith(".fifo") ? "1" : message.EnvironmentId
};
On ReceiveMessage, we retrieve that value back via --attribute-names MessageGroupId.
aws sqs receive-message \
--queue-url <url> \
--attribute-names MessageGroupId \
--max-number-of-messages 1
Floci silently discards MessageGroupId on SendMessage for standard queues (which is correct per AWS spec), so ReceiveMessage returns no MessageGroupId attribute.
Are you willing to contribute a PR?
Service
SQS
API Action / Feature
SendMessage — MessageGroupId parameter on standard (non-FIFO) queues
AWS Documentation
SendMessage — MessageGroupId parameter on standard (non-FIFO) queues
ReceiveMessage — MessageGroupId system attribute
Why is this needed?
Our application sends messages to standard (non-FIFO) SQS queues using the AWS SDK's SendMessageRequest with MessageGroupId set to a caller-supplied correlation value (an EnvironmentId GUID):
On ReceiveMessage, we retrieve that value back via --attribute-names MessageGroupId.
Floci silently discards MessageGroupId on SendMessage for standard queues (which is correct per AWS spec), so ReceiveMessage returns no MessageGroupId attribute.
Are you willing to contribute a PR?