AWS iot-mi documentation change
Summary
Removed mention of specific interfaces (Console/CLI/API) where permissions are denied by default, and simplified explanation about IAM policy assignment process.
Security assessment
The change removes redundant details about access denial through specific interfaces but doesn't address a security vulnerability or weakness. It maintains the core security concept of least-privilege permissions through IAM policies without introducing new security-related information.
Diff
diff --git a/iot-mi/latest/devguide/security_iam_id-based-policy-examples.md b/iot-mi/latest/devguide/security_iam_id-based-policy-examples.md index beaeb20d4..d0a66ea89 100644 --- a//iot-mi/latest/devguide/security_iam_id-based-policy-examples.md +++ b//iot-mi/latest/devguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify managed integrations resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify managed integrations resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.