AWS iot documentation change
Summary
Removed specific references to AWS Management Console, AWS CLI, and AWS API in default permissions explanation while maintaining core IAM policy requirements
Security assessment
The change simplifies documentation about default permissions but doesn't address any specific vulnerability or security incident. It maintains the security-relevant information about IAM policies being required for access, but removes redundant interface-specific examples without altering security posture.
Diff
diff --git a/iot/latest/fleethubuserguide/security_iam_id-based-policy-examples.md b/iot/latest/fleethubuserguide/security_iam_id-based-policy-examples.md index 6863c6b48..e8c0810e5 100644 --- a//iot/latest/fleethubuserguide/security_iam_id-based-policy-examples.md +++ b//iot/latest/fleethubuserguide/security_iam_id-based-policy-examples.md @@ -11 +11 @@ AWS will discontinue the AWS IoT Device Management Fleet Hub feature on October -By default, users and roles don't have permission to create or modify Fleet Hub 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 Fleet Hub resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.