Skip to content

eventbridge pipes to FIFO SQS dynamic message id pattern created #2764

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

boomtown15
Copy link

Issue #, if available:

Description of changes:

Adding new Serverless pattern (eventbridge-pipes-dynamic-message-group-id) that demonstrates how to dynamically set an SQS FIFO Queue message group ID from details in the event body passed through EventBridge and onto SQS. This is not something currently supported by InputTransformers and has been encountered by AWS customers recently. I'm looking to publish this pattern to ensure we have a solution readily in place.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

"authors": [
{
"name": "Kurt Tometich",
"image": "https://drive.google.com/uc?export=view&id=16K9snJRzXYTI7O0nYbzrKVYP58xOxciB",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Image URL is not working


3. Build and deploy the SAM application
```bash
sam build && sam deploy --guided
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need sam build or only deploy is sufficient?

@@ -0,0 +1,61 @@
{
"title": "EventBridge Pipes Dynamic Message Group Id",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Please use Full Service name on first use e.g. Amazon EventBridge, Amazon SQS.
  2. Please give a meaningful title.

@@ -0,0 +1,61 @@
{
"title": "EventBridge Pipes Dynamic Message Group Id",
"description": "Uses EventBridge Pipes to dynamically retrieve and set the message group ID for a SQS FIFO destination queue",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazon SQS

{
"title": "EventBridge Pipes Dynamic Message Group Id",
"description": "Uses EventBridge Pipes to dynamically retrieve and set the message group ID for a SQS FIFO destination queue",
"language": "",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YAML

@@ -0,0 +1,86 @@
# Assigning a dynamic message group ID from the message body using EventBridge Pipes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazon EventBridge Pipes

@@ -0,0 +1,86 @@
# Assigning a dynamic message group ID from the message body using EventBridge Pipes

EventBridge, a serverless event bus service, and SQS, a managed message queuing service, work together in event-driven architectures to route and process messages between AWS services and applications. While EventBridge routes messages to SQS queues for processing by microservices, FIFO queues can be used for strict message ordering. Although EventBridge cannot directly set message group IDs for organizing related messages, EventBridge Pipes provides a solution by allowing dynamic message group ID assignment based on event properties, enabling ordered processing for specific users, applications, or locations without additional coding.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazon SQS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants