AWS Security ChangesHomeSearch

AWS prescriptive-guidance documentation change

Service: prescriptive-guidance · 2026-03-07 · Documentation low

File: prescriptive-guidance/latest/strategy-matter-standard/cloud-connectivity-with-matter.md

Summary

Updated documentation about Matter OTA update limitations (1.4.2) and added camera/media streaming capabilities (1.5). Expanded vendor integration examples and hub listings. Enhanced section headers and CSA standardization status.

Security assessment

The changes describe functional improvements (transport reliability in OTA updates) and new capabilities (camera streaming). While OTA reliability could indirectly impact security update delivery, there is no explicit mention of security vulnerabilities, patches, or security-focused features. The additions are operational/functional enhancements rather than security documentation.

Diff

diff --git a/prescriptive-guidance/latest/strategy-matter-standard/cloud-connectivity-with-matter.md b/prescriptive-guidance/latest/strategy-matter-standard/cloud-connectivity-with-matter.md
index 3a2d8e3c1..7cd20b36b 100644
--- a//prescriptive-guidance/latest/strategy-matter-standard/cloud-connectivity-with-matter.md
+++ b//prescriptive-guidance/latest/strategy-matter-standard/cloud-connectivity-with-matter.md
@@ -21 +21,3 @@ Although Matter handles local device interoperability, additional cloud connecti
-  * **Over-the-air (OTA) updates** – Delivering firmware and software updates over the internet allows vendors to easily enhance devices that are already deployed. Without OTA, updates would be handled manually. While Matter standard describes how the OTA updates are handled and delivered to Matter-certified endpoints, it is dependent on the functionality supported by the Matter hub that the endpoint is connected to. Additionally, there are restrictions regarding which updates are provided to the endpoint. For example, when the endpoint requests an update, only the latest update available is provided. All devices of the same type are provided that single update. There is no option to do a sequential update or even an OTA rollback or deletion of an update. Enabling cloud connectivity on the endpoint can mitigate this lack of fine-grained management of OTA updates.
+  * **Over-the-air (OTA) updates** – Delivering firmware and software updates over the internet allows vendors to easily enhance devices that are already deployed. Without OTA, updates would be handled manually. While Matter standard describes how the OTA updates are handled and delivered to Matter-certified endpoints, it is dependent on the functionality supported by the Matter hub that the endpoint is connected to. Additionally, there are restrictions regarding which updates are provided to the endpoint. For example, when the endpoint requests an update, only the latest update available is provided. All devices of the same type are provided that single update. There is no option to do a sequential update or even an OTA rollback or deletion of an update. Enabling cloud connectivity on the endpoint can mitigate this lack of fine-grained management of OTA updates. Matter version 1.4.2 (June 2025) introduced improvements to transport reliability and testing infrastructure that have enhanced OTA update mechanisms. However, the fundamental limitations around sequential updates and rollback capabilities remain, making direct cloud connectivity valuable for manufacturers that require fine-grained update control and fleet management capabilities.
+
+  * **Camera streaming and media** – Matter version 1.5 (November 2025) introduced camera support using side-channel protocols, such as Real-Time Streaming Protocol (RTSP) over Wi-Fi or Ethernet. While Matter handles device discovery and basic control, the actual video streaming occurs through separate protocols. This often requires cloud infrastructure for remote viewing, recording, and AI-based features, such as person detection.
@@ -27 +29 @@ Although Matter handles local device interoperability, additional cloud connecti
-  * **Vendor-specific integrations** – Any custom features and data types that are not defined in the Matter specification require connectivity to vendor cloud platforms.
+  * **Vendor-specific integrations** – Any custom features and data types that are not defined in the Matter specification require connectivity to vendor cloud platforms. This is particularly important for devices with advanced features like cameras (Matter version 1.5), energy management devices (Matter version 1.4), and appliances (Matter versions 1.2-1.3) that may require manufacturer-specific cloud services for full functionality.
@@ -40 +42 @@ For Matter devices, there are three general approaches to providing the necessar
-_Smart-home hub with built-in gateway_
+### Smart-home hub with built-in gateway
@@ -44 +46 @@ Some device makers might choose to ship a proprietary home hub that incorporates
-_Offload cloud connectivity to an existing Matter hub_
+### Offload cloud connectivity to an existing Matter hub
@@ -46 +48 @@ _Offload cloud connectivity to an existing Matter hub_
-Rather than bundle a custom hub, devices could be designed to connect with Matter hubs like Amazon Echo or Google Home for internet connectivity. In this case, the existing Matter hub handles local device communication according to the standard, and it also provides a gateway to the cloud for endpoints that require it. This takes advantage of infrastructure consumers might already have. However, this approach depends on the level of support offered by the Matter hub for features that are not specified as normative for Matter hubs in the standard.
+Rather than bundle a custom hub, devices could be designed to connect with Matter hubs, such as Amazon Echo, Google Nest Hub, Apple HomePod, or Samsung SmartThings Hub, for internet connectivity. In this case, the existing Matter hub handles local device communication according to the standard, and it also provides a gateway to the cloud for endpoints that require it. This takes advantage of infrastructure consumers might already have. However, this approach depends on the level of support offered by the Matter hub for features that are not specified as normative for Matter hubs in the standard.
@@ -48 +50 @@ Rather than bundle a custom hub, devices could be designed to connect with Matte
-_Direct cloud connectivity in endpoints_
+### Direct cloud connectivity in endpoints
@@ -54 +56 @@ Devices with direct internet connectivity, such as Wi-Fi, could integrate separa
-While Matter simplifies local interoperability, additional effort is required to smoothly connect Matter admin systems and manufacturer cloud platforms. Organizations such as the Connectivity Standards Alliance (CSA) are working to standardize how Matter devices interface with the cloud for capabilities such as OTA updates. Widely adopting standards for this cloud connectivity would make ease development for device makers.
+While Matter simplifies local interoperability, additional effort is required to smoothly connect Matter admin systems and manufacturer cloud platforms. The Connectivity Standards Alliance (CSA) continues to develop standards for Matter-to-cloud connectivity. As of 2026, while formal cloud interface standards are still evolving, industry best practices have emerged from the deployment of thousands of Matter devices. Widely adopting standards for this cloud connectivity would ease development for device makers.