Hi everyone! I have my EventBridge set up to send events to an SQS FIFO queue, but I've run into an issue. The event body includes an event ID and timestamps, which means the hashed output for deduplication is different each time, even if the relevant data in the **detail** field is identical. I'm wondering if there's a simple workaround for this. Would using EventBridge input transformations help me modify the body to only include the **detail**, or rearranging the **id** and **time** fields outside of the **body**? Here's an example of the event body I'm working with:
'body': '{"version":"0","id":"c76d719f-bb24-4945-bda3-3f162a57c8ce","detail-type":"Mapping","source":"<source>","account":"<account_num>","time":"2025-05-16T19:32:13Z","region":"us-east-1","resources":[],"detail":{<event_detail>}}}'
3 Answers
It’s actually possible to provide your own deduplication string! Just keep in mind that if the source sending the events to the bus isn't under your control, you might have limitations.
Yes, you can definitely use input transformations to customize what gets sent to your SQS. If you're using an EventBridge pipe, this should make it easier for you to control the output.
Input transformations can be a nice solution! Just ensure you effectively filter out the unwanted fields. That way, your deduplication should work based on the core information you need.
We're not currently using a pipe. Just a basic EventBridge bus to event target.
EDIT: looks like input transformations will work, thanks!