AWS iot-fleetwise documentation change
Summary
Simplified explanation of default permissions by removing explicit mention of AWS Management Console, CLI, and API access restrictions. Focus retained on IAM policies granting necessary permissions.
Security assessment
The change removes redundant details about access methods (console/CLI/API) but does not alter the core security principle of least-privilege IAM policies. No evidence of addressing a specific vulnerability or weakness. This is a documentation clarity improvement rather than a security-related update.
Diff
diff --git a/iot-fleetwise/latest/developerguide/security_iam_id-based-policy-examples.md b/iot-fleetwise/latest/developerguide/security_iam_id-based-policy-examples.md index 54b7aafb2..e58265599 100644 --- a//iot-fleetwise/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//iot-fleetwise/latest/developerguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsA -By default, users and roles don't have permission to create or modify AWS IoT FleetWise 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 FleetWise resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.