AWS IoT Core Documentation

The AWS IoT Device SDK helps you connect your hardware device or your mobile application to AWS IoT Core. The AWS IoT Device SDK is designed to enable your devices to connect, authenticate, and exchange messages with AWS IoT Core using the MQTT, HTTP, or WebSockets protocols. The AWS IoT Device SDK is designed to support C, JavaScript, and Arduino, and includes the client libraries, the developer guide, and the porting guide for manufacturers. You can also use an open source alternative or write your own SDK.

Device Advisor is a fully managed cloud-based test capability for validating IoT devices during development. It provides pre-built tests that help developers validate their IoT devices for connectivity with AWS IoT Core. Device Advisor helps developers test if their IoT devices can interoperate with AWS IoT Core and follow security best practices. Developers can more easily identify and resolve the most common device software issues during development before they deploy their devices in production. Device Advisor also provides a signed qualification report which can be used by hardware partners to qualify their devices for inclusion in the AWS Partner Device Catalog.

The Device Gateway serves as the entry point for IoT devices connecting to AWS. The Device Gateway is designed to manage all active device connections and implement semantics for multiple protocols to help validate that devices are able to efficiently communicate with AWS IoT Core. For devices that connect using MQTT or WebSockets the Device Gateway is designed to maintain long lived, bidirectional connections, helping these devices to send and receive messages with low latency. The Device Gateway is fully managed and designed to scale to support over a billion devices without requiring you to manage any infrastructure. For customers migrating to AWS IoT, the Device Gateway offers capabilities designed to transition infrastructures with minimal impact to existing architectures and IoT devices.

The Message Broker is a high throughput pub/sub message broker that is designed to transmit messages to and from your IoT devices and applications with low latency. The flexible nature of the Message Broker’s topic structure helps you to send messages to, or receive messages from, as many devices as you would like. It is designed to support messaging patterns ranging from one-to-one command and control messaging, to one-to-one million (or more) broadcast notification systems and everything in between. The Message Broker is a fully managed service designed to scale with your message volume without requiring you to run any infrastructure.

AWS IoT Core is designed to provide mutual authentication and encryption at all points of connection. With AWS IoT Core you can use AWS IoT Core generated certificates, as well as those signed by your preferred Certificate Authority (CA). The service is designed so you can map your choice of policies to each certificate, so that you can authorize devices or applications to have access, or change your mind and revoke access altogether without ever touching the device.

The Registry is designed to establish an identity for devices and track metadata such as the devices’ attributes and capabilities. The Registry is designed to assign a unique identity to each device that is consistently formatted regardless of the type of device or how it connects. It also supports metadata that describes the capabilities of a device, for example whether a sensor reports temperature, and if the data are Fahrenheit or Celsius. Metadata in the Registry may expire if you do not access or update your registry entry within the period of time designated by AWS.

With AWS IoT Core, you can create a persistent, virtual version, or Device Shadow, of each device that is designed to include the device’s latest state so that applications or other devices can read messages and interact with the device. The Device Shadow is designed to persist the last reported state and desired future state of each device even when the device is offline. You can retrieve the last reported state of a device or set a desired future state through the API or using the rules engine.

The Rules Engine helps you build IoT applications that gather, process, analyze and act on data generated by connected devices at global scale without having to manage any infrastructure. The Rules Engine is designed to evaluate inbound messages published into AWS IoT Core and transform and deliver them to another device or a cloud service, based on business rules you define. A rule can apply to data from one or many devices, and it can take one or many actions in parallel.

AWS IoT Core for LoRaWAN is designed to help customers connect wireless devices that use low-power, long-range wide area network (LoRaWAN) technology. Using AWS IoT Core, customers can setup a private LoRaWAN network by connecting their own LoRaWAN devices and gateways to the AWS Cloud - without developing or operating a LoRaWAN Network Server (LNS).

AWS IoT Core Device Location helps you track and manage your fleet of IoT devices using their location data, such as latitude and longitude coordinates, without traditional Global Positioning Service (GPS) hardware. For example, Device Location helps your field service team can identify the location of devices that require maintenance action, and can also support location-based security enhancements, such as restricting access to a specific Region.

Amazon Sidewalk is a shared network that helps connected devices work better through improved connectivity options. Operated by Amazon, Sidewalk can help simplify new device setup, extend the low-bandwidth working range of devices, and help devices stay online even if they are outside the range of their home Wi-Fi.

For additional information about service controls, security features and functionalities, including, as applicable, information about storing, retrieving, modifying, restricting, and deleting data, please see https://docs.aws.amazon.com/index.html. This additional information does not form part of the Documentation for purposes of the AWS Customer Agreement available at http://aws.amazon.com/agreement, or other agreement between you and AWS governing your use of AWS’s services.