aws-events
TLDR
List all rules in the default event bus
SYNOPSIS
aws events subcommand [options]
DESCRIPTION
aws events is a subcommand of the AWS CLI that manages Amazon EventBridge (formerly CloudWatch Events), a serverless event bus service. It routes events between AWS services, SaaS applications, and your own applications.
Rules match incoming events based on patterns and route them to targets like Lambda functions, Step Functions, SNS topics, SQS queues, and more. Rules can also trigger on schedules using cron or rate expressions.
Event buses act as routers: the default bus receives AWS service events, while custom buses can receive events from your applications. Partner event sources connect to SaaS providers.
PARAMETERS
list-rules
List rules on an event bus.describe-rule
Get details about a specific rule.put-rule
Create or update a rule.delete-rule
Remove a rule.enable-rule
Activate a disabled rule.disable-rule
Deactivate a rule without deleting it.list-targets-by-rule
List targets attached to a rule.put-targets
Add targets to a rule.remove-targets
Remove targets from a rule.list-event-buses
List event buses in the account.put-events
Send custom events to an event bus.--name rule-name
Name of the rule.--schedule-expression expression
Cron or rate expression for scheduled rules.--event-pattern json
JSON pattern to match events.--targets targets
Target specifications (Id, Arn, Input, etc.).--event-bus-name name
Event bus name (default if not specified).
CAVEATS
Must remove all targets before deleting a rule. Schedule expressions use UTC timezone. Event patterns match on exact values by default; use prefix or anything-but for flexibility. Maximum 5 targets per rule (can be increased via quota request). Rules can take up to one minute to become active.
HISTORY
CloudWatch Events launched in January 2016 as AWS's first event-driven integration service. It was rebranded as Amazon EventBridge at AWS re:Invent 2019 with expanded capabilities including custom event buses and third-party SaaS integrations. Schema registry and discovery were added to help developers understand event structures. The service continues to be central to serverless and event-driven architectures on AWS.
SEE ALSO
aws(1), aws-lambda(1), aws-sns(1), aws-sqs(1)


