Overview
A client-mode connector for a curated cloud-IoT slice of AWS IoT SiteWise covering property ingest from UNS topics, property history queries, and asset create from Sparkplug birth:
Default
BASE_ADDRESS is data-plane https://data.iotsitewise.eu-west-1.amazonaws.com (no trailing slash; substitute {region}). Topics use cloud-iot/aws-iot-sitewise/<object>/<verb>.
See the base guide: REST API Connectors.
Control-plane ops: set
BASE_ADDRESS to https://api.iotsitewise.{region}.amazonaws.com for CreateAsset and ListAssets. SigV4 service name on both planes is iotsitewise.Data-plane SigV4: 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
- Sign each request with AWS Signature Version 4 using service name
iotsitewise(both planes). - Map signed values into MQTT JSON:
authorization,x_amz_date,x_amz_content_sha256(and optional STS session token). - Store
AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEYas Hub secrets for the upstream signer — never in the deployable.lot. - Use data-plane BASE for BatchPut / history; switch to control-plane BASE (
api.iotsitewise.{region}.amazonaws.com) for CreateAsset / ListAssets.
Related
- REST API Connectors
- AWS IoT Core (same SigV4 placeholder pattern)
- Amazon S3 (same SigV4 placeholder pattern)
- BatchPutAssetPropertyValue
- GetAssetPropertyValueHistory
- CreateAsset
- ListAssets
- SiteWise endpoints

