What is managed integrations for AWS IoT Device Management?
Managed integrations for AWS IoT Device Management helps IoT solution providers unify the control and management of IoT devices from hundreds of manufacturers. You can use managed integrations to automate device setup workflows and to support interoperability across many devices, regardless of device vendor or connectivity protocol. This allows solution providers to use a single user interface and set of APIs to control, manage, and operate a range of devices.
Topics
Are you a first-time managed integrations user?
If you are a first-time user of managed integrations, we recommend that you begin by reading the following sections:
Managed integrations overview
The following image provides a high-level overview of managed integrations
Managed integrations terminology
Within managed integrations, there are many concepts and terms critical to understand for managing your own device implementations. The following sections outline those key concepts and terms to provide a better understanding of managed integrations.
General managed integrations terminology
An important concept to understand for managed integrations is a Managed Thing compared to an AWS IoT Core thing.
-
AWS IoT Core thing: An AWS IoT Core Thing is an AWS IoT Core construct that provides the digital representation. Developers are expected to manage policies, data storage, rules, actions, MQTT topics, and delivery of device state to the data storage. For more information on what an AWS IoT Core thing is, see Managing devices with AWS IoT.
-
Managed integrations Managed Thing: With a Managed Thing, we provide an abstraction to simplify device interactions and do not require the developer to create items such as rules, actions, MQTT Topics, and policies.
Cloud-to-cloud terminology
Physical devices that integrate with managed integrations may originate from a third-party cloud provider. To onboard those devices to managed integrations and communicate with the third-party cloud provider, the following terminology covers some of the key concepts supporting those workflows:
-
Cloud-to-cloud (C2C) connector: A C2C connector establishes a connection between managed integrations and the third-party cloud provider.
-
Third-party cloud provider: For devices that are manufactured and managed outside of managed integrations, a third-party cloud provider enables control of these devices for the end user and managed integrations communicates with the third-party cloud provider for various workflows such as device commands.
Data model terminology
Managed integrations uses data models for organizing data and end-to-end communication between your devices. The following terminology covers some of the key concepts for understanding those two data models:
-
Device: An entity representing a physical device (such as a video doorbell) which has multiple nodes working together to provide a complete feature set.
-
Endpoint: An endpoint encapsulates a standalone feature (ringer, motion detection, lighting in a video doorbell).
-
Capability: An entity representing components which are needed to make a feature available in an endpoint (button or a light and chime in the bell feature of video doorbell).
-
Action: An entity representing an interaction with a capability of a device (ring the bell or view who’s at the door).
-
Event: An entity representing an event from a capability of a device. A device can send an event to report an incident/alarm, an activity from a sensor etc. (e.g. there is knock/ring on the door).
-
Property: An entity representing a particular attribute in device state (bell is ringing, porch light is on, camera is recording).
-
Data Model: The data layer corresponds to the data and verb elements that help support the functionality of the application. The Application operates on these data structures when there is an intent to interact with the device. For more information, see connectedhomeip
on the GitHub website. -
Schema: A schema is a representation of the data model in JSON format.
