A freight broker must reshape each EventBridge event into the JSON a ticket API accepts. The application that publishes the event cannot be changed. What should they add?
Select an answer to reveal the explanation.
Short Explanation
You do not rebuild the printing press to change the envelope one mailbox receives. The ticket API needs its own JSON shape, and an EventBridge input transformer on the target maps the event without a second publisher. Forking the producer would tie every future change to two emitters, and the producer cannot be changed anyway.
Full Explanation
An input transformer on an EventBridge target pulls fields from the event and builds the body that target receives. The ticket API gets the schema it expects, and the publisher keeps emitting the original event for every other consumer. The transformer does not rewrite the event at the source, so other rules on the bus still see the original payload. A second code path in the publisher is a fork of the producer, and it is ruled out because that application cannot be changed. Another bus that forwards the original body does not reshape the payload, so the ticket API still sees the producer schema. An archive retains events for replay and is not a mapping step in front of the API. Caveat: the transformer applies to the target you configure, not to every other target on the rule, so a second subscriber still gets the original event unless it has its own transformer. Operational check: send a test event, capture the body that arrives at the ticket API, and confirm the mapped fields match the schema while the event on the bus is unchanged.