feat(events-targets): support messageGroupId for standard SQS queues #36068
+163
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EventBridge now supports the messageGroupId parameter for standard (non-FIFO) SQS targets. This change removes the client-side validation that was blocking this feature. Fixes: Removes ValidationError when messageGroupId is used with standard queues Tests: Updated test to verify messageGroupId works with standard queues Docs: Updated JSDoc to reflect support for both queue types
github-actions
bot
added
p2
beginning-contributor
aws-cdk-automation
previously requested changes
Nov 14, 2025
…sageGroupId - Added comprehensive README documentation showing messageGroupId usage for both FIFO and standard queues - Updated integration test to include messageGroupId example with standard queue - Addresses PR feedback requiring README and integration test changes
Added CloudFormation resources for standard queue with messageGroupId: - StandardQueue resource - StandardQueuePolicy with EventBridge permissions - StandardQueueRule with SqsParameters.MessageGroupId
aws-cdk-automation
dismissed
their stale review
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
This was referenced Nov 15, 2025
Author
|
The integration test "destructive changes" are intentional and expected. I've added three new resources to the integration test to demonstrate the messageGroupId feature with standard (non-FIFO) SQS queues:
These resources are necessary to validate that messageGroupId now works correctly with standard queues, which is the core functionality being added in this PR. The existing test only covered FIFO queues and encrypted queues with dead letter queues - this addition provides coverage for the new standard queue capability. |
awesomelike
approved these changes
Nov 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
EventBridge now supports the
messageGroupIdparameter for standard (non-FIFO) SQS targets. This PR removes the client-side validation that was preventing customers from using this feature.Changes
SqsQueueconstructor that blocked messageGroupId for standard queuesBackground
The EventBridge service API has always supported messageGroupId as an optional parameter for SqsParameters, but the service validation previously rejected it for standard queues. With the recent backend service change (CR-231214910), EventBridge now accepts messageGroupId for standard SQS queues, enabling customers to use this parameter for message grouping.
Testing
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license