EventBridge Bus, Rule & Target
A custom EventBridge event bus, a pattern-filtered rule, and a target wired end-to-end - encryption at rest always on, least-privilege log delivery, and a 24h retry policy with optional DLQ.
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan test superseded by live test
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o aws-eventbridge-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/aws-eventbridge/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle aws-eventbridge-1.0.0.sigstore.json \
aws-eventbridge-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "68820e942f40cba6aac62d9a6a902747732be62f0648520ce24eddd7b0d679b2 aws-eventbridge-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "eventbridge" {
source = "www.iac-bazaar.com/iac-bazaar/aws-eventbridge/aws"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/aws-eventbridge?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [EventBridge Bus, Rule & Target](https://www.iac-bazaar.com/catalog/aws-eventbridge?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "eventbridge" {
source = "www.iac-bazaar.com/iac-bazaar/aws-eventbridge/aws"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
aws-eventbridge
A custom Amazon EventBridge event bus, a rule that filters events by
event pattern, and a target — wired end-to-end. Works with Terraform and
OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
By default the module creates its own CloudWatch Logs group as the target
(plus the resource policy EventBridge needs to write to it), so the whole stack
stands up from a single input (bus_name) and is perfect for capturing or
auditing events. Point it at any existing destination instead with
target_type = "external" and target_arn.
Secure defaults:
- Encryption at rest always on — the bus uses the AWS-owned EventBridge key
by default (free); pass
bus_kms_key_identifierfor a customer-managed key. The target log group is encrypted with AWS-managed CloudWatch Logs encryption unless you supplylog_kms_key_id. - Least-privilege log delivery — the log group resource policy grants only
logs:CreateLogStream/logs:PutLogEvents, scoped to that single group and guarded by anaws:SourceAccountcondition so only this account's EventBridge can write (confused-deputy protection). - Reliable delivery — a 24h / 185-attempt retry policy by default, with an optional dead-letter queue on both the bus and the target.
Custom-bus rules must filter by event pattern — AWS only allows
schedule_expressionrules on the default bus, so this module intentionally does not expose scheduling (use theaws-step-functions/EventBridge Scheduler for that). The default pattern is a catch-all ({"account": ["<id>"]}); setevent_patternfor real routing.
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/aws>= 6.0, < 7.0
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Inputs
- Outputs
Related modules
aws-mq
deployment_mode defaults to SINGLE_INSTANCE, and Amazon MQ reboots the instance to patch it - so a single broker has planned downtime on AWS's schedule. Active/standby across two AZs, both log streams on, and passwords in a separate variable from users, because a sensitive value cannot be a for_each argument at all.
aws-kinesis-firehose
Without error_output_prefix, records Firehose could not process are written into the same prefix as the ones it could, wrapped in an error envelope that whatever reads the prefix treats as data. Nothing reports it.
aws-kinesis
A Kinesis Data Stream with KMS encryption at rest on by default and ON_DEMAND capacity (no shard math), plus optional enhanced fan-out consumers and IAM-only access.
aws-msk
An MSK Serverless Apache Kafka cluster with no brokers to size - SASL/IAM authentication only, encryption in transit and at rest always on, multi-AZ placement, and a locked-down security group.
aws-ses
An SES v2 sending stack - a configuration set with an optional domain/email identity (Easy DKIM) - with TLS required, bounce/complaint suppression, and reputation metrics to CloudWatch.
aws-sns
SNS standard/FIFO topic with encryption, delivery policies, and SQS/Lambda/email subscriptions.