EventBridge
Last updated: Nov 3, 2026
Rationale
Amazon EventBridge is the service that Fluid Attacks uses for event routing and to schedule workloads in the cloud. With it, Fluid Attacks can react to changes in its AWS infrastructure, route events between services, and run recurring jobs on a schedule, without infrastructure management. These are the primary reasons why Fluid Attacks selected it and not other alternatives:
- It is a fully managed serverless service. There is no infrastructure to provision or manage, and it scales automatically with the volume of events.
- It integrates easily with AWS services, for example, Lambda, Batch, and CloudWatch. Thus, Fluid Attacks can connect producers and consumers with very little configuration.
- It complies with many certifications from ISO and CSA. Many of these certifications make sure that the entity uses best practices for secure cloud-based environments and information security.
- It supports schedule-based rules with cron and rate expressions, for recurring workloads.
- It supports event pattern matching to filter and route events by their content and structure.
- It gives built-in retry policies and dead-letter queues. This makes it more reliable when targets fail.
- It supports cross-region event routing through custom event buses. Thus, Fluid Attacks can collect events from more than one region into a central bus.
Alternatives
- Google Cloud Eventarc: It gives event-driven orchestration on GCP. But to use it, Fluid Attacks would have to support one more cloud provider, and its stack and knowledge would be in more parts.
- Azure Event Grid: It gives event routing on Azure. But Fluid Attacks would have to manage a second cloud platform, and this adds complexity and operational work.
- Amazon SNS / Amazon SQS: They are good for basic pub/sub and message queuing, but they do not have native schedule expressions or content-based event pattern matching.
- Cron on EC2: The user must manage infrastructure. It does not have built-in retry or routing capabilities, and it does not integrate natively with other AWS services.
Usage
Fluid Attacks uses EventBridge for these tasks:
- To schedule Batch jobs, Lambda functions, and Step Functions state machines for ETLs, background processes, and CI tasks, for example, to clean environments or remove branches
- To report failed Batch jobs to make metrics
- To tell the development mailing list about the cost anomalies that Cost Anomaly Detection finds
- To tell the development mailing list about the security findings that GuardDuty finds
Other AWS services, for example, EKS, Inspector, or Step Functions, also make EventBridge triggers.