Device types Configure encryption key Onboarding techniques

Get started with managed integrations for AWS IoT Device Management

The following sections outline the steps that you need to take to start using managed integrations.

Topics

Device types
Configure encryption key
Onboarding techniques

Device types

Managed integrations manages many types of devices. Each device is within one of the following three categories:

Direct-connected devices: This type of device directly connects to an managed integrations endpoint. Typically, these devices are built and managed by device manufacturers that include the managed integrations end device SDK for the direct connectivity.
Hub-connected devices: These devices connect to managed integrations through a hub running the managed integrations Hub SDK, which manages device discovery, onboarding, and control functions. End-users can onboard these devices using button press initiation or barcode scanning.

The following two workflows are supported for onboarding a hub-connected device:
- An end user initiated button press to start device discovery
- Barcode-based scanning to perform the device association
Cloud-to-cloud (C2C) devices: These are devices that are designed and managed by vendors that maintain their own cloud infrastructure and branded mobile applications for device control. Managed integrations customers can access a catalog of pre-built C2C connectors or create their own, to develop IoT solutions that work with multiple third-party vendor clouds through a unified interface.

When the end user powers on a C2C device for the first time, it must be provisioned with its respective third-party cloud provider for managed integrations to obtain its device capabilities and metadata. After completing that provisioning workflow, managed integrations can communicate with the cloud device and the third-party cloud provider on behalf of the end user.

Note

A hub is not a specific device type as listed above. Its purpose is serving the role as a controller of smart home devices and facilitating a connection between managed integrations and third-party cloud providers. It can serve the role as both a device type as listed above and as a hub.

Configure encryption key

Security is of paramount importance for data routed between the end user, managed integrations, and third-party clouds. One of the methods we support to protect your device data is end-to-end encryption leveraging a secure encryption key for routing your data.

As a customer of managed integrations, you have the following two options for using encryption keys:

Use the default managed integrations-managed encryption key.
Provide an AWS KMS key that you created.

For more information on the AWS KMS service, see Key management service (KMS)

Calling the PutDefaultEncryptionConfiguration API in the Managed integrations API Reference Guide grants you access to update which encryption key option you want to use. By default, managed integrations uses the default managed integrations managed encryption key. You can update your encryption key configuration at any time using the PutDefaultEncryptionConfiguration API.

Additionally, calling the GetDefaultEncryptionConfiguration API command returns information about the encryption configuration for the AWS account in the default or specified region.