Replaying dead-letter messages across Azure, AWS and GCP, and saying "verification required" when it can't be proven

Description and use

ServiceHub manages dead‑letter queue messages across Azure, AWS, and GCP, offering failure‑reason grouping, replay previews, success verification, and an immutable recovery ledger.

Problem

When queues back up, messages land in dead‑letter queues and teams instinctively replay them, but they lack visibility into why failures occurred, whether the root cause is fixed, who replayed what, and whether the replay succeeded.

Outcome

ServiceHub enables teams to understand failure reasons, safely replay messages with preview gates, verify replay success where possible, automate replay with safety mechanisms, and maintain an immutable ledger of recoveries.

Workflow

• 1. View dead‑letter queues per cloud; failures are grouped by reason.
• 2. Press "Look now" for AWS/GCP to read up to 100 messages and store them locally.
• 3. Click "Replay" on a message or "Replay All" for a group; ServiceHub shows a proposal with scope, sample, risk, policy, and stop condition.
• 4. If all checks pass, the replay is executed; otherwise it is blocked.
• 5. For Azure, ServiceHub confirms whether replayed messages stayed out of the dead‑letter queue; for AWS/GCP it marks the replay as "verification required".
• 6. Auto Replay rules are applied per failure signature, with circuit breakers, emergency stops, and back‑off if recent replays failed.
• 7. All recoveries are written to a hash‑chained ledger visible in the Advanced view.

Evidence

"I hit these on every cloud I work with, so I built ServiceHub: a self-hosted, MIT-licensed tool for Azure Service Bus, AWS SQS/SNS and GCP Pub/Sub."

Source

"every replay, whether a person clicks it or the Agent does it, goes through one gate. Before anything is sent it shows a proposal: scope, a sample, the risk, the policy and the stop condition."

Source

"Azure can confirm whether a replayed message stayed out of the dead‑letter queue. AWS and GCP can't, without extra infrastructure."

Source

"The Agent replays on its own only for a failure signature it has earned trust on, per signature, not globally."

Source

"every recovery is written to a hash‑chained ledger you can read in Advanced."

Source