Integrations

OPC UA to AWS IoT SiteWise, without a script.

Read the OPC UA nodes with MaestroHub, give each value a governed name and unit, and send them to SiteWise asset properties in batches. MaestroHub can create the asset models and assets automatically from property aliases, and buffers writes when the link drops.

The flow

One value, from the machine to AWS IoT SiteWise. Illustrative.

OPC UAindustrial protocolns=2;s=Comp2.Pressure

MaestroHub

Compressor 2 pressure · 6.8 bar · Good

named, unit, quality
origin stamped
buffered on disk

AWS IoT SiteWiseindustrial cloud service/plant/line2/compressor2/pressure

Why do it with MaestroHub

More than a pipe from OPC UA to AWS IoT SiteWise.

Assets created for you

Zero-touch auto-modelling builds SiteWise models and assets from the aliases, instead of clicking them together.

Not tied to one cloud

The same values can go to SiteWise and to a warehouse or broker outside AWS, each with its own buffer.

Quality passes through

SiteWise receives each value's quality and timestamp as MaestroHub verified them.

What lands in AWS IoT SiteWise

An example. You choose the fields in the pipeline.

alias	value	quality	timestamp
/plant/line2/compressor2/pressure	6.8	GOOD	2026-10-03T06:00:01Z

Set it up in three steps

1
Connect OPC UA
Add the OPC UA server, browse its address space and pick the nodes, or add hundreds at once with bulk creation.
2
Give the values meaning
Map each value to a topic in the namespace with its name, unit and schema. Quality and origin are stamped on every value.
3
Deliver to AWS IoT SiteWise
Add a SiteWise output; assets and models can be created automatically from the property aliases you send.

Before you start

What each side needs, from the connector documentation.

OPC UA

The server address, built as opc.tcp://host:port/path. The standard OPC UA port is 4840.
For any Security Policy other than None, a client certificate: paste your own (RSA keys only) or let MaestroHub generate a self-signed one.
If you use the auto-generated certificate, the OPC UA server administrator must trust it on the server.
A username and password when the server does not allow Anonymous access.

Example settings

Server Hostname: opcua.example.com
Port: 4840
Security Policy: Basic256Sha256
Security Mode: SignAndEncrypt
Certificate Mode: Auto-generate (self-signed)
Authentication Type: UsernamePassword

OPC UA connector documentation

AWS IoT SiteWise

The AWS region of your SiteWise resources. Custom regions such as us-gov-west-1 can be entered.
AWS credentials: an access key ID and secret access key together, or both left empty to use IAM roles and the default credential chain (recommended on EC2, ECS and EKS).
For SiteWise Edge or a VPC endpoint: the endpoint URL for the Custom Endpoint field.

Example settings

Region: us-east-1
Default Batch Size: 10
Property Alias (Write): /factory/motor-001
Data (Write): {"temperature": ((temp)), "rpm": ((speed))}
Quality (Write): GOOD
Schema Hints (Write): {"temperature": "DOUBLE"}

AWS IoT SiteWise connector documentation

Things to know

Pitfalls and limits the documentation calls out, so they don't surprise you on site.

OPC UA

Security Policy and Security Mode must agree. Policy None requires Mode None. Any other policy requires Sign or SignAndEncrypt.
Node identifiers need a namespace index and a type prefix (i=, s=, g=, b=). Namespace 0 is typically standard nodes, 2 and up custom nodes. Browse a small scope first to find the exact IDs.
On Monitor functions, set the sampling interval equal to or faster than the publishing interval, or changes can be missed. Subscriptions are recreated automatically after a lost connection or a session timeout.

Limits

Manual client certificates support RSA keys only. Auto-generated certificates are RSA 2048-bit and valid for 365 days.
Monitor functions cannot be created through Quick Add. Use the full Function Builder.

AWS IoT SiteWise

Store & Forward is off by default. Until you turn it on for the connection under Orchestrate, Store & Forward, a failed write is not buffered or retried.
Whole numbers are inferred as INTEGER, so a temperature of 25 becomes INTEGER. Use Schema Hints such as {"temperature": "DOUBLE"} to force the type.
Auto-Create Model & Asset is meant for prototyping. In production, pre-create models and assets and use explicit property aliases.

Limits

AWS accepts at most 10 entries per BatchPutAssetPropertyValue call. The connector splits larger payloads into chunks.

What teams use it for

SiteWise dashboards and alarms

Live asset views for operations teams in AWS.

Fleet monitoring

The same asset structure across plants and lines.

Feeding AWS analytics

SiteWise data onward to S3, Athena or SageMaker.

Ways to connect OPC UA to AWS IoT SiteWise

In general terms. Check any specific product for its own details.

Compare a custom script, a flow tool, a cloud vendor's edge service and MaestroHub

Swipe sideways to see every column

	A custom script	A flow tool	A cloud vendor's edge service	MaestroHub
Talks OPC UA	A library you choose	Community plug-ins	Depends on the vendor	Built in, one of 90+ connectors
Names, units and schema	You write it	You build it	Partly, in the vendor's model	One governed namespace
Quality on every value	You write it	You build it	Depends on the vendor	Built in, carried through calculations
Where each value came from	You write it	You build it	Depends on the vendor	Stamped on every value
Survives a network outage	You build it	You build it	Usually, to that vendor's cloud	On disk, per destination, in order
Several destinations at once	One script each	Yes, flow by flow	Mostly that vendor's cloud	Any mix, each with its own buffer
Permissions and audit	You build it	You build it	Cloud account permissions	Roles, single sign-on, audit trail
AI agents can use the data	You build it	You build it	Depends on the vendor	Through the MCP server

Questions

How do I connect OPC UA data to AWS IoT SiteWise?

Do I need to write code to connect OPC UA to AWS IoT SiteWise?

No. You configure the OPC UA connection and the AWS IoT SiteWise output in MaestroHub and join them with a pipeline. Transformations can be added where you need them.

Where does MaestroHub run for this?

On your own infrastructure next to the machines: an edge box, a virtual machine or Kubernetes. Nothing has to leave your network.

Why not just write a script for OPC UA to AWS IoT SiteWise?

A script works on day one. The cost comes later: decoding and naming values, handling bad quality, buffering through outages, keeping credentials safe, and doing it again for the next machine and the next destination. MaestroHub does those once, for every connector.

What else can OPC UA data go to?

More than 90 connectors are included in every edition, among them historians, databases, cloud warehouses, message brokers and business systems, so the same values can feed several destinations at once.

Other integrations

All integrations