AWS iot-twinmaker documentation change
Summary
Removed explicit mention of users being unable to perform tasks via AWS Management Console, CLI, or API by default. Simplified the explanation of default permissions.
Security assessment
The change simplifies documentation wording but does not introduce or address any specific security vulnerability. The core security principle (default deny permissions) remains intact. No evidence of a security incident or weakness being patched.
Diff
diff --git a/iot-twinmaker/latest/guide/security_iam_id-based-policy-examples.md b/iot-twinmaker/latest/guide/security_iam_id-based-policy-examples.md index 32bb2f3e8..235da0ded 100644 --- a//iot-twinmaker/latest/guide/security_iam_id-based-policy-examples.md +++ b//iot-twinmaker/latest/guide/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 AWS IoT TwinMaker 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 AWS IoT TwinMaker resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.