canonical: https://jentic.com/apis/amazonaws.com/amazon-cloudwatch-events # AWS Amazon CloudWatch Events Jentic publishes the only available OpenAPI specification for Amazon CloudWatch Events (now Amazon EventBridge), keeping it validated and agent-ready. EventBridge is AWS's serverless event bus for routing events between AWS services, custom applications, and SaaS partners. The API manages event buses, routing rules, targets, archives and replays, API destinations, connections, and partner event sources. It is built for engineering teams that need an event backbone for cross-service automation without running their own message broker. ## For AI agents Route events between AWS services, custom apps, and SaaS partners with EventBridge - manage event buses, rules, targets, and archives. ## Scope Does not handle queueing, pub-sub topics, log aggregation, or in-process tracing - use for event bus routing, scheduling, and partner event ingestion only. ## Capabilities - Create custom event buses and partner event buses for cross-account routing - Define rules with detail-type, source, and content-based event patterns - Add up to five targets per rule including Lambda, SQS, Step Functions, and API destinations - Configure API destinations and HTTP connections for outbound events to external systems - Archive events on a bus and replay archived events back through rules for backfill - Activate and deactivate event sources from SaaS partners such as Datadog and PagerDuty - Schedule rules with cron and rate expressions to trigger targets on a recurring basis ## Use cases ### Cross-Service Event Automation Engineering teams use EventBridge to wire up cross-service automation such as triggering downstream workflows when an EC2 instance changes state, an S3 object is uploaded, or a Step Functions execution finishes. The API creates rules with pattern matching and attaches targets so a single event can fan out to multiple consumers. This replaces brittle service-to-service polling with a declarative event bus. Example prompt: Create a rule on the default event bus that matches AWS events with source aws.s3 and detail-type Object Created, then add a Lambda function as the target. ### Scheduled Workflow Triggers Operations teams use EventBridge schedule rules with cron and rate expressions to trigger Lambda functions, ECS tasks, and Step Functions state machines on a fixed cadence. This replaces ad-hoc cron servers and dedicated scheduler infrastructure with a managed scheduling surface inside AWS. Rules support cron expressions down to one-minute granularity. Example prompt: Create a rule named hourly-cleanup with schedule expression rate(1 hour) and add Lambda function arn:aws:lambda:...:function:cleanup as a target. ### Partner SaaS Event Ingestion Platform teams use EventBridge partner event sources to ingest events from SaaS providers such as Datadog, PagerDuty, and Zendesk into AWS workflows. The API activates partner sources, attaches them to a partner event bus, and routes them to internal targets. This lets internal automation react to third-party events without building a webhook receiver. Example prompt: Activate the partner event source aws.partner/datadog.com/events and attach it to a new event bus named datadog-events. ### Agent-Driven Event Routing via Jentic AI agents use the EventBridge API through Jentic to wire up new automation in response to system events such as alerts, deploys, or business metrics crossing thresholds. Jentic exposes EventBridge operations as discoverable tools so an agent can search by intent and create rules with targets in seconds. This lets agents build out reactive infrastructure without console steps. Example prompt: Search Jentic for create eventbridge rule, load the PutRule schema, and execute it with name onboarding-trigger and event pattern matching detail-type SignupCompleted. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /#X-Amz-Target=AWSEvents.CreateEventBus | Create a custom event bus | | POST | /#X-Amz-Target=AWSEvents.CreateArchive | Create an archive on an event bus | | POST | /#X-Amz-Target=AWSEvents.CreateApiDestination | Create an outbound API destination | | POST | /#X-Amz-Target=AWSEvents.CreateConnection | Create an HTTP connection for API destinations | | POST | /#X-Amz-Target=AWSEvents.CreatePartnerEventSource | Create a partner event source | | POST | /#X-Amz-Target=AWSEvents.ActivateEventSource | Activate a partner event source | | POST | /#X-Amz-Target=AWSEvents.CancelReplay | Cancel a running event replay | ## Key resources - **Event Buses** — Default, custom, and partner event buses for routing - **Rules** — Event patterns and schedule expressions matching events to targets - **Targets** — Lambda, SQS, Step Functions, API destinations, and other downstream consumers - **Archives** — Stored event copies for replay and backfill - **Connections and API Destinations** — Outbound HTTP destinations with managed authentication ## Why Jentic - **Setup:** Wiring Amazon EventBridge by hand means building SigV4 request signing, resolving the regional events.{region}.amazonaws.com host, and handling the X-Amz-Target action dispatch plus AWS retries yourself. Through Jentic you install once, import CloudWatch Events from the API Directory, store the AWS access keys once, and your agent calls it. - **Permission scoping:** EventBridge dispatches every action through a single endpoint with the operation named in the request, so scope the agent to the operations it needs, such as creating an event bus, archive, or connection. Destructive operations like canceling a replay stay out of that set unless you add them. - **Credential handling:** Your AWS access keys for EventBridge are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an event rule' or 'add a partner event source', and Jentic returns the matching EventBridge operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **AWS Lambda** — Most common EventBridge target for executing custom logic on incoming events - **AWS Step Functions** — Orchestrates multi-step workflows triggered by EventBridge rules - **Amazon CloudWatch** — Provides metrics and alarms that can fire EventBridge events ## FAQ ### Why is there no official OpenAPI spec for Amazon CloudWatch Events? AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon CloudWatch Events via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Amazon EventBridge API use? EventBridge uses AWS Signature Version 4 request signing. Through Jentic, AWS access keys are stored encrypted in the vault and signing happens server-side, so the agent never sees the raw secret access key. ### Can I schedule rules to trigger on a cron expression? Yes. PutRule accepts a ScheduleExpression with cron or rate syntax (for example cron(0 * * * ? *) or rate(5 minutes)). The rule fires its targets on the schedule with at-least-once delivery. ### What are the rate limits for the Amazon EventBridge API? AWS applies per-account, per-region throttling on the management API. Default event bus PutEvents has a separate, higher data-plane limit. Use exponential backoff on ThrottlingException responses; AWS does not publish exact TPS numbers in the spec. ### How do I add a Lambda target to a rule through Jentic? Search Jentic for add eventbridge target, load the PutTargets schema, and execute it with the rule name and a Targets entry containing the Lambda function ARN. Jentic returns FailedEntries if the target could not be added. ### Does this API replace SQS or SNS? No. EventBridge routes structured events between sources and rule-matched targets. SQS provides queueing and SNS provides pub-sub topics. EventBridge can use SQS or SNS as a target, but it does not replicate their delivery semantics. ### Can I limit what my agent is allowed to do with the Amazon EventBridge API? Yes. Because Jentic One is self-hosted, you decide which EventBridge operations and which AWS credentials your agent may use, and your own rules are enforced at execution time. EventBridge dispatches every action through a single endpoint with the operation named in the request, so you scope the agent to just the operations it needs, such as creating an event bus, an archive, or a connection. Destructive operations like canceling a replay stay outside that set unless you explicitly add them.