A customer action should trigger work without making the customer wait for every step.

When this becomes useful

An action in one part of the product needs to start work elsewhere. An event boundary lets each side evolve, provided the event contract and failure handling are clear.

What the template offers

HTTP API to EventBridge is a Terraform pattern from AWS Serverless Patterns. It offers a concrete implementation to inspect and adapt. Useful when an API request should enqueue an event instead of doing all work inline. Define delivery, replay and consumer idempotency separately.

Technical shape

Inspect how the HTTP request becomes an EventBridge event and how the event bus and target permissions are configured.

Questions worth answering

• Who owns the event schema?
• What happens when consumers fail?
• Can an event be replayed safely?

Inspect the source

Read the maintainer's README, license, setup instructions and current repository state before adapting the code.