Amazon CloudWatch Events

Name: Amazon CloudWatch Events API
Brand: Amazon CloudWatch Events
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey51 EndpointsREST

For Agents

Route events between AWS services, custom apps, and SaaS partners with EventBridge — manage event buses, rules, targets, and archives.

Connect the Amazon CloudWatch Events to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon CloudWatch Events, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Amazon CloudWatch Events API.

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

GET STARTED

Start building with Amazon CloudWatch Events API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon CloudWatch Events, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Amazon CloudWatch Events API for, with concrete tasks.

★ 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.

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.

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.

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.

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

51 endpoints — jentic publishes the only available openapi specification for amazon cloudwatch events (now amazon eventbridge), keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys for EventBridge are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing access — raw secret access keys never enter the agent context.

Intent-based discovery

Agents search by intent (for example create an event rule) and Jentic returns matching EventBridge operations with their input schemas, so the agent can call the right action without browsing AWS docs.

Time to first call

Direct EventBridge integration: 1-2 days for SigV4 signing, event pattern formatting, and target permissions. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Lambda

Most common EventBridge target for executing custom logic on incoming events

Choose Lambda when an event should trigger custom code rather than route to another AWS service.

Complementary

AWS Step Functions

Orchestrates multi-step workflows triggered by EventBridge rules

Choose Step Functions when an event should kick off a stateful workflow with retries and branching, not a single function call.

Complementary

Amazon CloudWatch

Provides metrics and alarms that can fire EventBridge events

Choose CloudWatch when the trigger is an alarm state change or metric threshold rather than a service event.

FAQs

Specific to using Amazon CloudWatch Events API through Jentic.

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 at https://app.jentic.com/sign-up.

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.