Archive EventBridge events and replay them to a target after a deployment rollback
domain: aws-eventbridge · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create an archive on the event bus: specify a source event-bus ARN, an optional event pattern filter, and a retention period in days (0 = indefinite)
Confirm the archive is in ENABLED state and the EventCount is incrementing via the console or aws events describe-archive
After a failed deployment, create a replay: aws events start-replay --replay-name my-replay --source-archive-arn <archive-arn> --event-start-time <ISO8601> --event-end-time <ISO8601> --destination EventBus={Arn:<bus-arn>}
Monitor replay state with aws events describe-replay until State is COMPLETED
Replayed events are injected into the target bus and will trigger all matching rules; use a temporary rule with a dedicated target during replay if you need to isolate replayed events from live ones
Delete the replay resource after completion; archives continue to accumulate future events
Known gotchas
EventBridge now supports event payloads up to 1 MB; payloads exceeding this limit must use the claim-check pattern (store large data in S3 and publish only a reference pointer in the event)
Replayed events contain a replay-name field in the detail; downstream consumers that need to distinguish replays from live events should inspect this field
Only events matching the archive's event pattern at the time they were originally published are stored; you cannot retroactively replay events that were not captured by the archive
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?