AWS IoT Events

Name: AWS IoT Events API
Brand: AWS IoT Events
Availability: InStock

★ Only Publicly Available SpecIOTSensor Datahmac26 EndpointsREST

For Agents

Define and version AWS IoT Events inputs, detector models, and alarm models that turn IoT telemetry into stateful event-driven automation across equipment fleets.

Quickstart

Get started with AWS IoT Events in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an aws iot events detector model"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AWS IoT Events API.

Create and version inputs that describe the schema of incoming telemetry messages

Create and version detector models — state machines that fire actions on transitions

Create and manage alarm models that watch numeric inputs against thresholds

Run analyses on detector models to surface logic errors before deployment

GET STARTED

Start building with AWS IoT Events API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for AWS IoT Events, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS IoT Events, keeping it validated and agent-ready. AWS IoT Events monitors equipment and device fleets for failures or changes in operation by running detector models — state machines that react to incoming telemetry inputs. The control-plane API manages inputs, detector models, alarm models, model versions, and detector model analyses across 26 operations. It is the configuration surface for setting up event-driven automation on top of IoT telemetry.

Use Cases

Patterns agents use AWS IoT Events API for, with concrete tasks.

★ Predictive Maintenance State Machines

Model failure-warning logic for industrial equipment as a detector model — for example, a state machine that tracks temperature, vibration, and runtime hours, transitioning to a 'pre-failure' state when thresholds combine. Each transition can fire SNS, Lambda, or IoT Events Republish actions to alert maintenance crews. Detector model versions support staged rollouts.

Call CreateDetectorModel with detectorModelDefinition containing two states (Normal, Warning), a transition condition on $input.temperature.value > 80, and an SNS publish action on entry to Warning

Threshold Alarm Management

Use alarm models to watch a single numeric input against high and low thresholds without writing detector model logic. CreateAlarmModel and UpdateAlarmModel manage the watchers, and DescribeAlarm tracks current state including ACK and SNOOZE. Alarm models are simpler than detector models for one-metric guardrails.

Call CreateAlarmModel with alarmRule.simpleRule comparing inputProperty $input.tankSensor.level < 5.0 and severity 4

Pre-Deployment Logic Validation

Run StartDetectorModelAnalysis on a draft detector model to surface unreachable states, missing transitions, and unused inputs before publishing it to the fleet. GetDetectorModelAnalysisResults returns analysis findings keyed by detector model state. This shortens the iteration loop for engineers building complex state machines.

Call StartDetectorModelAnalysis with a detectorModelDefinition payload, then GetDetectorModelAnalysisResults using the returned analysisId

AI Agent IoT Operations

Through Jentic, an AI agent can operate IoT Events as a configuration surface — adding alarm models when an operator describes a new threshold, listing existing detector models, or rolling forward a new detector model version. Jentic exposes the 26 operations as discoverable tools.

Search Jentic for 'create aws iot events alarm model', load the CreateAlarmModel schema, and execute it with the alarmRule and roleArn

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for aws iot events, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/detector-models

CreateDetectorModel — create a new detector model

GET

/detector-models

ListDetectorModels — list detector models

GET

/detector-models/{detectorModelName}

DescribeDetectorModel — fetch a detector model definition

POST

/inputs

CreateInput — define a new input schema

GET

/inputs

ListInputs — list inputs in the account

POST

/alarm-models

CreateAlarmModel — create an alarm model

GET

/alarm-models

ListAlarmModels — list alarm models

GET

/alarm-models/{alarmModelName}

DescribeAlarmModel — fetch an alarm model

POST

/detector-models

CreateDetectorModel — create a new detector model

GET

/detector-models

ListDetectorModels — list detector models

GET

/detector-models/{detectorModelName}

DescribeDetectorModel — fetch a detector model definition

POST

/inputs

CreateInput — define a new input schema

GET

/inputs

ListInputs — list inputs in the account

Why though Jentic?

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

Credential isolation

AWS access keys for IoT Events are stored encrypted in the Jentic vault. Agents never see the raw credentials — Jentic signs each request with SigV4 server-side.

Intent-based discovery

Agents search Jentic with intents like 'create iot events detector model' or 'list alarm models' and get the matching operation back with its input schema.

Time to first call

Direct integration: 1-2 days to wire up the AWS SDK, IAM roles, and detector model definitions. Through Jentic: under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS IoT Data Plane

Source of MQTT telemetry that feeds IoT Events inputs

Use IoT Data Plane to publish telemetry; use IoT Events to react to that telemetry with stateful logic.

Complementary

AWS IoT SiteWise

Industrial asset modelling that pairs with IoT Events for equipment-level alarms

Use SiteWise to model assets and store time-series metrics; use IoT Events to attach alarm and detector logic to that data.

Complementary

AWS Lambda

Lambda is a common action target invoked by IoT Events transitions

Use Lambda to handle IoT Events action invocations; use IoT Events to define when those Lambdas fire.

FAQs

Specific to using AWS IoT Events API through Jentic.

Why is there no official OpenAPI spec for AWS IoT Events?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS IoT 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 AWS IoT Events API use?

The API uses AWS Signature Version 4 (HMAC) request signing with an AWS access key ID and secret access key. Through Jentic, AWS credentials are stored encrypted in the vault and the agent calls signed operations without seeing the raw keys.

Can I create a detector model with the AWS IoT Events API?

Yes. Call POST /detector-models with a detectorModelName, a detectorModelDefinition containing states and transitions, and a roleArn that IoT Events uses to invoke actions. The model is versioned, and you can publish a new version with UpdateDetectorModel.

What are the rate limits for the AWS IoT Events API?

AWS applies per-account, per-region request quotas to IoT Events operations and these vary by call. Detector model creation has lower quotas than list and describe operations. Check AWS Service Quotas for current limits.

How do I run a detector model analysis through Jentic?

Search Jentic for 'analyze aws iot events detector model', load the StartDetectorModelAnalysis schema, and execute with the detectorModelDefinition payload. Then call GetDetectorModelAnalysisResults using the returned analysisId to read findings.

What is the difference between a detector model and an alarm model?

A detector model is a full state machine with multiple states, transitions, and actions. An alarm model is a simpler single-input threshold watcher with built-in ACK and SNOOZE behaviour. Use alarm models for straightforward threshold alerts and detector models for multi-step logic.