Skip to main content
Technical Preview

Overview

A client-mode connector for a curated cloud-IoT slice of AWS IoT Core covering registry, Jobs/OTA, classic Device Shadow, and HTTPS data-plane publish (no MQTT bridge): Default BASE_ADDRESS is control-plane https://iot.eu-west-1.amazonaws.com (no trailing slash; substitute {region}). Topics use cloud-iot/aws-iot-core/<object>/<verb>. See the base guide: REST API Connectors.
Data-plane Publish: set BASE_ADDRESS to your ATS endpoint from aws iot describe-endpoint --endpoint-type iot:Data-ATS (for example https://xxxxxx-ats.iot.eu-west-1.amazonaws.com). SigV4 service name on the data plane is iotdevicegateway (port 443). X.509 on :8443 is AWS-supported but outside this LoT template.
Control-plane SigV4 service name is iot. Pass Authorization, x-amz-date, and x-amz-content-sha256 from an upstream signer via MQTT JSON placeholders. Prefer Hub secrets for AWS keys — never commit them into the .lot.
Prefer Hub secrets for AWS keys used by an upstream SigV4 signer. This template has not been verified against a live AWS account. Status remains blocked until an authenticated live smoke succeeds.

Basic Syntax

Configuration

MQTT topics

Auth details

  1. Sign each request with AWS Signature Version 4 using the correct service name (iot on control plane; iotdevicegateway on data-plane Publish).
  2. Map signed values into MQTT JSON: authorization, x_amz_date, x_amz_content_sha256 (and optional STS session token).
  3. Store AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY as Hub secrets for the upstream signer — never in the deployable .lot.
Last modified on October 21, 2026