A Terraform module for creating and managing AWS EventBridge resources including buses, rules, targets, archives, and schedules.
terraform-aws-eventbridge is a Terraform module that automates the provisioning and management of AWS EventBridge resources. It solves the problem of manually configuring complex event-driven infrastructure by providing a declarative, reusable code module that handles buses, rules, targets, permissions, and related services. This enables developers to consistently deploy and manage event-driven workflows on AWS.
DevOps engineers, platform engineers, and cloud architects who use Terraform to manage AWS infrastructure and need to implement event-driven patterns with EventBridge.
Developers choose this module because it encapsulates AWS EventBridge's complexity into a well-tested, community-maintained Terraform module, reducing boilerplate code, ensuring best practices, and providing extensive configuration options for production deployments.
Terraform module to create AWS EventBridge resources 🇺🇦
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports all major EventBridge components including buses, rules, targets, permissions, pipes, schedules, and archives, as evidenced by the extensive usage examples and input variables.
Offers boolean flags like create_bus and create_rules to conditionally create resources, enabling modular and reusable configurations without duplication.
Automates IAM policy attachments for common targets like Lambda and Step Functions, with multiple ways to add custom policies via policy_json or policy_statements, as detailed in the README.
Designed with AWS and Terraform best practices, providing sensible defaults for logging, archiving, and security while allowing extensive customization for complex use cases.
With over 50 input variables, configuring the module can be verbose and overwhelming for simple setups or newcomers, leading to potential errors.
The module is tightly coupled to AWS services and Terraform, making it unsuitable for multi-cloud deployments or teams using alternative IaC tools like Pulumi.
Users rely on module maintainers to update it for new AWS features or API changes, which could lag behind official releases and cause compatibility issues.