Amazon CloudWatch Events Amazon EventBridge
Serverless event bus, point-to-point event pipe, and task scheduling service that connects applications using events from AWS services, SaaS partners, and custom systems.
Naming timeline
- Amazon CloudWatch Events
Launched as a capability within Amazon CloudWatch on the events API namespace to route near-real-time AWS system events and cron schedules to targets such as AWS Lambda.
- Amazon EventBridgeCurrent name
Expanded and rebranded Amazon CloudWatch Events into Amazon EventBridge with custom event buses and third-party SaaS integrations while sharing the exact same default event bus and events API primitives.
What is Amazon CloudWatch Events called now?
Amazon CloudWatch Events is now called Amazon EventBridge, with the latest change on 11 July 2019 (AWS New York Summit 2019 Launch). Serverless event bus, point-to-point event pipe, and task scheduling service that connects applications using events from AWS services, SaaS partners, and custom systems. Only the customer-facing name changed; the underlying technical identifiers remain backward compatible.
Also known as
- CloudWatch Events
- EventBridge Event Bus
- EventBridge Scheduler
- EventBridge Pipes
Technical identifiers
Technical identifiers unchanged. Only the customer-facing product name changed; the APIs, CLI commands, IAM roles and Terraform resources below keep their legacy identifiers for backward compatibility.
| AWS Service APIs / SDKs | events scheduler pipes schemas |
|---|---|
| AWS CLI Commands | aws events aws scheduler aws pipes aws schemas |
| IAM Actions & Policies | events:* scheduler:* pipes:* schemas:* |
| Terraform Resources (aws_*) | aws_cloudwatch_event_bus aws_cloudwatch_event_rule aws_cloudwatch_event_target aws_cloudwatch_event_permission aws_scheduler_schedule aws_pipes_pipe |
EventBridge event buses, rules, and targets continue to use the events API, aws events CLI, events:* IAM actions, and aws_cloudwatch_event_* Terraform resources (with docs.aws.amazon.com/AmazonCloudWatch/latest/events/ redirecting to EventBridge docs).
Notes & disambiguation
- On July 11, 2019, AWS evolved and rebranded Amazon CloudWatch Events into Amazon EventBridge, building directly on the underlying CloudWatch Events service architecture while adding custom event buses, SaaS partner event sources, and schema discovery.
- Core EventBridge event bus operations continue to use the original CloudWatch Events technical identifiers for backward compatibility: the events API namespace, aws events CLI commands, events:* IAM actions, AWS::Events::* CloudFormation resources, and aws_cloudwatch_event_* Terraform resources (e.g., aws_cloudwatch_event_rule, aws_cloudwatch_event_target).
- Newer standalone capabilities launched under the EventBridge family use dedicated technical namespaces, including EventBridge Schemas (schemas / aws_schemas_*), EventBridge Scheduler (scheduler / aws_scheduler_schedule), and EventBridge Pipes (pipes / aws_pipes_pipe).
Sources & official documentation
Catalog last updated . Spotted an error? Suggest an edit