AWS deadline-cloud documentation change
Summary
Removed mention of default inability to use AWS Management Console/CLI/API without permissions, focusing documentation on resource modification permissions
Security assessment
The change simplifies the explanation of default permissions but doesn't address any specific security vulnerability or weakness. While IAM policies are security-related, this edit appears to be a documentation clarification rather than a response to a security issue.
Diff
diff --git a/deadline-cloud/latest/userguide/security_iam_id-based-policy-examples.md b/deadline-cloud/latest/userguide/security_iam_id-based-policy-examples.md index 84d4bc7b3..c1bee3a2e 100644 --- a//deadline-cloud/latest/userguide/security_iam_id-based-policy-examples.md +++ b//deadline-cloud/latest/userguide/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.