EventBridge replay lets you reprocess events after a consumer bug fix

An EventBridge archive keeps the events of a bus so that past events can be sent back to it later. A replay resends a chosen time range, which lets teams correct data that a buggy consumer handled wrongly before the fix. Events reach the archive with a short delay, so AWS advises waiting at least ten minutes before replaying, and replay order is not guaranteed. Replayed events carry a replay-name field and are filtered out of the archive, so they are not stored twice. Because old events reach every matching consumer unless rules are filtered, a replay should be limited to the affected rule, and replay is not a substitute for retries or dead-letter queues.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in