Industrial IoT / SCADA · API / SDK

AWS IoT Core API

AWS

Manage connected-device resources in the AWS IoT service.

Official documentation Download development spec

AWS IOT CORE / DEVELOPER FIELD GUIDE

Choose an interface. Define a verifiable result.

Company or project context, ten technical entry points and a practical analysis of every reference.

2026-10-08 · Integration not tested

Company / project overview

Original summary of official company or project statements; use the source for the full original page.

AWS IoT Core · About
Service	AWS IoT Core connects device fleets with cloud messaging and rule-based data integration.
Implementation boundary	Device connectivity, cloud state and downstream business completion are separate evidence layers.

Complete official About page ↗

About reference — TA analysis
Audience	Buyers, partners and product owners shortlisting an AI provider.
Our assessment	Use positioning and company history for initial fit. Obtain project-specific deployment, support and commercial terms separately.

Official sources reviewed. No provider API or inference was run; results are illustrative internal contracts.

Top 10 technical entry points

Ten documented technical entry points selected for implementation decisions, not ten independent SDKs or an official ranking.

Choose by the work you need to complete
Interface	Purpose and audience
01 · Device protocolsAPI / SDK / developer guide	Choose MQTT/WSS publish-subscribe or HTTPS publishing.Connectivity engineers
02 · Device SDK selectionAPI / SDK / developer guide	Select maintained language/device clients.Firmware developers
03 · Device Shadow topicsAPI / SDK / developer guide	Get, update and delete cloud state using reserved topics.Device-state integrators
04 · Rules engineAPI / SDK / developer guide	Filter MQTT streams and invoke configured service actions.Data integration engineers
05 · IoT policy actionsAPI / SDK / developer guide	Authorize connection, publish, subscription and receipt separately.Security engineers
06 · Fleet provisioningAPI / SDK / developer guide	Provision unique device credentials from templates.Fleet onboarding teams
07 · IoT JobsAPI / SDK / developer guide	Coordinate remote device operations.Fleet operations
08 · Thing registryAPI / SDK / developer guide	Organize device resource identities and attributes.Asset integration teams
09 · CloudWatch loggingAPI / SDK / developer guide	Inspect message broker and rule processing events.Operations engineers
10 · HTTP Publish APIAPI / SDK / developer guide	Publish a payload to a topic via the data plane.Backend developers

Reference analysis

Capabilities summarize official documentation. Constraints and proposed tests are our engineering assessment.

API / SDK / developer guide

Device protocols

Device protocols · TA
Target audience	Connectivity engineers
Documented capability	Choose MQTT/WSS publish-subscribe or HTTPS publishing.
Input → output	Topic payload and connection options → broker transport.
Execution environment	Account endpoint; protocol-specific TLS/authentication.
Our decision constraint	HTTPS does not provide MQTT subscriptions.
Our suggested validation	Verify reconnect handling and the documented port/auth combination.

Official reference · Device protocols ↗

API / SDK / developer guide

Device SDK selection

Device SDK selection · TA
Target audience	Firmware developers
Documented capability	Select maintained language/device clients.
Input → output	Connection configuration → MQTT messages and callbacks.
Execution environment	Choose platform-compatible SDK and pin its version.
Our decision constraint	Earlier SDK generations are maintenance-only; avoid them for new projects.
Our suggested validation	Confirm target OS, TLS and MQTT support before porting.

Official reference · Device SDK selection ↗

API / SDK / developer guide

Device Shadow topics

Device Shadow topics · TA
Target audience	Device-state integrators
Documented capability	Get, update and delete cloud state using reserved topics.
Input → output	Shadow request → accepted/rejected response or delta.
Execution environment	Named/classic shadow topics and topic authorization.
Our decision constraint	Cloud desired state is not physical execution evidence.
Our suggested validation	Correlate accepted/rejected messages and device-reported state.

Official reference · Device Shadow topics ↗

API / SDK / developer guide

Rules engine

Rules engine · TA
Target audience	Data integration engineers
Documented capability	Filter MQTT streams and invoke configured service actions.
Input → output	Topic message and rule → downstream action.
Execution environment	AWS resource permissions and destination configuration.
Our decision constraint	Actions require access and can incur destination service charges.
Our suggested validation	Separate unmatched conditions from authorization/action failures.

Official reference · Rules engine ↗

API / SDK / developer guide

IoT policy actions

IoT policy actions · TA
Target audience	Security engineers
Documented capability	Authorize connection, publish, subscription and receipt separately.
Input → output	Principal, action and resource → allow/deny.
Execution environment	IoT policy scoped to appropriate resource types.
Our decision constraint	Subscribe permission alone does not grant Receive.
Our suggested validation	Test authorized topic and prohibited cross-device topic.

Official reference · IoT policy actions ↗

API / SDK / developer guide

Fleet provisioning

Fleet provisioning · TA
Target audience	Fleet onboarding teams
Documented capability	Provision unique device credentials from templates.
Input → output	Claim or trusted-user flow → certificate and registered thing.
Execution environment	Provisioning template, role and protected bootstrap credentials.
Our decision constraint	Ownership tokens expire; bootstrap claims are not normal device credentials.
Our suggested validation	Verify reconnect with permanent certificate and no private-key logging.

Official reference · Fleet provisioning ↗

API / SDK / developer guide

IoT Jobs

IoT Jobs · TA
Target audience	Fleet operations
Documented capability	Coordinate remote device operations.
Input → output	Job document and targets → per-device execution progress.
Execution environment	Jobs service plus device-side job handler.
Our decision constraint	Job creation does not mean device execution completed.
Our suggested validation	Require terminal execution evidence from intended devices.

Official reference · IoT Jobs ↗

API / SDK / developer guide

Thing registry

Thing registry · TA
Target audience	Asset integration teams
Documented capability	Organize device resource identities and attributes.
Input → output	Thing metadata → registry record.
Execution environment	Regional AWS IoT control plane permissions.
Our decision constraint	Registry presence is not proof of connectivity.
Our suggested validation	Map business asset identity to the intended thing.

Official reference · Thing registry ↗

API / SDK / developer guide

CloudWatch logging

CloudWatch logging · TA
Target audience	Operations engineers
Documented capability	Inspect message broker and rule processing events.
Input → output	Enabled logging and operations → log events.
Execution environment	Configure logging and CloudWatch access.
Our decision constraint	A missing log group may mean no logging/events, not a healthy fleet.
Our suggested validation	Correlate topic/client events with destination observations.

Official reference · CloudWatch logging ↗

API / SDK / developer guide

HTTP Publish API

HTTP Publish API · TA
Target audience	Backend developers
Documented capability	Publish a payload to a topic via the data plane.
Input → output	Topic, payload and QoS → HTTP status with empty success body.
Execution environment	Correct data endpoint and authorized signing/credentials.
Our decision constraint	HTTP 200 does not prove downstream processing or physical actuation.
Our suggested validation	Accept empty success body; separately verify consumer receipt.

Official reference · HTTP Publish API ↗

Official documentation

Official documentation · Supporting reference analysis
TA	Developers and technical product owners
Our validation advice	Pin the release and follow the target-specific support requirements before implementation.

Official reference · Official documentation ↗

04 / INPUT · EXPECTED OUTPUT · ACCEPTANCE

Expected results before implementation

Illustrative telemetry delivery contract; no AWS account, certificate, MQTT connection or API call was used.

Illustrative contract · no API call or model execution · not measured provider output

Telemetry received

Expected behavior — illustrative, not executed
Input	Synthetic event on authorized topic.
Expected result	Publish accepted and consumer records matching event ID.
Acceptance	Validate payload mapping and deduplication separately from publish status.

Empty Publish response

Expected behavior — illustrative, not executed
Input	Successful HTTP Publish returns no body.
Expected result	accepted=true; consumer_verified remains false until observed.
Acceptance	Do not parse empty body as missing-data failure or invent delivery proof.

Device offline after desired-state update

Expected behavior — illustrative, not executed
Input	Shadow update accepted without a fresh reported state.
Expected result	Cloud update accepted; physical application pending.
Acceptance	Do not label actuator action complete from shadow acceptance.

Unauthorized topic

Expected behavior — illustrative, not executed
Input	Credential lacks Publish for target topic.
Expected result	Denied operation; no success evidence.
Acceptance	Surface authorization error without retrying indefinitely or exposing keys.

Map the expected result to your application

Map your actual runtime response into this proposed application contract. All values are invented examples; no credentials or live execution are included.

Expected output JSON — illustrative, not measured · AWSIoTCore-expected-results.json

{
  "schema_version": "1.0.0",
  "example": true,
  "provider": "AWS IoT Core",
  "status": "ok",
  "input_id": "sample-001",
  "data": {
    "topic": "factory/demo/temperature",
    "publish_accepted": true,
    "consumer_verified": true,
    "device_execution_verified": false,
    "event_id": "demo-event-001"
  },
  "error": null,
  "verification": "illustrative-only;not-provider-response"
}

Download specification, example and acceptance plan

Engineering handoff — our proposed contract and gates
State semantics	Valid empty results differ from errors. Pending work must not appear successful before completion.
Evidence	Record service and SDK versions, request identity, configuration and response mapping. No execution or performance was measured here.
Acceptance proposal	Agree numerical tolerances and workload targets before testing on representative authorized samples.

Development assessment

Connected-device registry

Development concept · integration not tested

Provider capabilities above are based on official documentation or repositories. The proposed product, inputs, deliverable and acceptance criteria below are our development assessment.

Integration pilot

Validate runtime, schemas or hardware together before estimating a deployable product.

Proposed inputs: A test device or simulator, a tag map and documented units.
Proposed deliverable: Timestamped device values with freshness, unit and connection state.
Acceptance criterion: Verify scaling and timestamps against the source; a disconnected device must not appear healthy.
Dependencies: A gateway or service account, an equipment schema and access to a test environment.

Development sequence

Confirm access to AWS IoT Core API, license and the exact supported version.
Prepare the sample above and implement one documented operation for “Connected-device registry”.
Normalize the result with source, time and explicit error state; keep the provider response for review.
Run the acceptance criterion before estimating rollout effort or committing a customer deliverable.

How to validate demand

Record product views, documentation clicks, specification downloads and contextual hub clicks. These are event counts, not unique people or completed integrations.

This feasibility assessment uses implementation conditions. No traffic-based rank or delivery-time promise is assigned.

AWS IoT Core API

Choose an interface. Define a verifiable result.

Company / project overview

Top 10 technical entry points

Reference analysis

Official documentation

Expected results before implementation

Telemetry received

Empty Publish response

Device offline after desired-state update

Unauthorized topic

Map the expected result to your application

Connected-device registry

Development sequence

How to validate demand

Related products