AWS deadline-cloud documentation change
Summary
Simplified introductory paragraph about IAM permissions by removing explicit mention of console/CLI/API access restrictions
Security assessment
The change removes redundant details about access methods (console/CLI/API) but maintains the core security principle of least privilege. This is a documentation refinement rather than a security fix or vulnerability disclosure.
Diff
diff --git a/deadline-cloud/latest/developerguide/security_iam_id-based-policy-examples.md b/deadline-cloud/latest/developerguide/security_iam_id-based-policy-examples.md index 45ef64972..2202029d3 100644 --- a//deadline-cloud/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//deadline-cloud/latest/developerguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consolePolicy to access the consolePolicy to subm -By default, users and roles don't have permission to create or modify Deadline Cloud 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 Deadline Cloud resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.