Product wants richer success payloads routed to a downstream event…

Question

Product wants richer success payloads routed to a downstream event bus when a Lambda finishes, not only failure capture after async retries. Which capability should the developer prefer?

Accepted Answer

Configure Lambda Destinations so both success and failure outcomes can route payloads to targets such as SQS, SNS, EventBridge, or another function. — DLQs are the failure locker; Destinations are the mailroom that can forward both success and failure packages with useful payloads. If product wants happy-path data on a bus, Destinations are the fit—not DLQ-only thinking.

Answer

Use only a dead-letter queue and discard all successful invocation results.

Answer

Disable async invoke and require every caller to ignore responses.

Answer

Replace Destinations with CloudTrail alone for application payload routing.

Product wants richer success payloads routed to a downstream event bus when a Lambda finishes, not only failure capture after async retries. Which capability should the developer prefer?

Short Explanation

Full Explanation