AWS iot-mi documentation change
Summary
Removed preview notice, simplified command/event descriptions, removed device state explanation section, and updated terminology (e.g. 'end-user' to 'end user', Matter Data Model capitalization)
Security assessment
Changes primarily involve content reorganization and terminology updates. While device commands mention security updates, the modifications don't introduce new security information or address specific vulnerabilities. Removal of device state explanation section reduces technical detail but doesn't impact security documentation.
Diff
diff --git a/iot-mi/latest/devguide/device-commands-events.md b/iot-mi/latest/devguide/device-commands-events.md index c3904d68b..c5b685116 100644 --- a//iot-mi/latest/devguide/device-commands-events.md +++ b//iot-mi/latest/devguide/device-commands-events.md @@ -7,2 +6,0 @@ Device commandsDevice Events -Managed integrations for AWS IoT Device Management is in preview release and is subject to change. For access, contact us from the [managed integrations console](https://console.aws.amazon.com/iot/home#/managed-integrations/intro). - @@ -11 +9 @@ Managed integrations for AWS IoT Device Management is in preview release and is -Device commands provide the ability to remotely manage a physical device ensuring complete control over the device in addition to performing critical security, software, and hardware updates. With a large fleet of devices, knowing when a device performs a command provides oversight over your entire device implementation. A device command or an automatic update will trigger a device state change, which in turn will create a new device event. This device event will trigger a notification automatically sent to a customer-managed destination to update the end-user. +Device commands provide the ability to remotely manage a physical device ensuring complete control over the device in addition to performing critical security, software, and hardware updates. With a large fleet of devices, knowing when a device performs a command provides oversight over your entire device implementation. A device command or an automatic update will trigger a device state change, which in turn will create a new device event. This device event will trigger a notification automatically sent to a customer-managed destination. @@ -24 +22 @@ Device commands provide the ability to remotely manage a physical device ensurin -A command request is the command being sent by the customer to the device. A command request includes a payload that specifies the action to be taken such as turning on the light bulb. To send a device command, the `SendManagedThingCommand` API is called on behalf of the end-user by managed integrations and the command request is sent to the device. +A command request is the command being sent to the device. A command request includes a payload that specifies the action to be taken such as turning on the light bulb. To send a device command, the `SendManagedThingCommand` API is called on behalf of the end user by managed integrations and the command request is sent to the device. @@ -120,4 +117,0 @@ A device event includes the current state of the device. This can mean the devic -**What is a device state?** - -The device state is described by a collection of resources. A resource refers to a set of capabilities that are described by a schema. Each resource state change has an associated version number. The resources associated with device can change over time as functionality is added or removed from the device. - @@ -126 +120 @@ The device state is described by a collection of resources. A resource refers to -An end-user can subscribe to specific customer-managed destinations that they create for updates on specific device events. To create a customer-managed destination, call the `CreateDestination` API. When a device event is reported to managed integrations by the device, the customer-managed destination is notified if one exists. +An end user can subscribe to specific customer-managed destinations that they create for updates on specific device events. To create a customer-managed destination, call the `CreateDestination` API. When a device event is reported to managed integrations by the device, the customer-managed destination is notified if one exists. @@ -134 +128 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -AWS implementation of the Matter Data Model +AWS implementation of matter data model @@ -136 +130 @@ AWS implementation of the Matter Data Model -Set up notifications +Managed integrations notifications