AWS iot-mi documentation change
Summary
Capitalized 'Managed Integrations' for consistency and corrected casing in resource policy description
Security assessment
Change involves capitalization consistency ('managed integrations' to 'Managed Integrations') without altering security content. The existing security guidance about resource policies and Condition keys remains unchanged.
Diff
diff --git a/iot-mi/latest/devguide/allow-iot-smart-home.md b/iot-mi/latest/devguide/allow-iot-smart-home.md index 8589509e6..5921fd44e 100644 --- a//iot-mi/latest/devguide/allow-iot-smart-home.md +++ b//iot-mi/latest/devguide/allow-iot-smart-home.md @@ -9 +9 @@ -AWS Lambda allows for resource-based policies to authorize who can invoke a Lambda. As managed integrations for AWS IoT Device Management is an AWS service, you must allow managed integrations to invoke your C2C connector Lambda via the resource policy. +AWS Lambda allows for resource-based policies to authorize who can invoke a Lambda. As managed integrations for AWS IoT Device Management is an AWS service, you must allow Managed Integrations to invoke your C2C connector Lambda via the resource policy. @@ -11 +11 @@ AWS Lambda allows for resource-based policies to authorize who can invoke a Lamb -Attach a resource policy with at least the following minimal permissions to your C2C connector Lambda. This provides managed integrations with Lambda function invoke privileges. This policy includes a `Condition` key to help you limit the usability of your `connectorId` to only intended users. +Attach a resource policy with at least the following minimal permissions to your C2C connector Lambda. This provides Managed Integrations with Lambda function invoke privileges. This policy includes a `Condition` key to help you limit the usability of your `connectorId` to only intended users.