AWS diagnostic-tools documentation change
Summary
Removed mention of default inability to perform tasks via AWS Console/CLI/API, focusing on default lack of permissions to create/modify resources.
Security assessment
The change simplifies the description of default permissions but does not address a specific security vulnerability or weakness. It clarifies existing IAM policy behavior rather than introducing new security controls or responding to a disclosed issue.
Diff
diff --git a/diagnostic-tools/latest/userguide/security_iam_id-based-policy-examples.md b/diagnostic-tools/latest/userguide/security_iam_id-based-policy-examples.md index 63811e604..59007c5d5 100644 --- a//diagnostic-tools/latest/userguide/security_iam_id-based-policy-examples.md +++ b//diagnostic-tools/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllowing all operations on the Diagnostic -By default, users and roles don't have permission to create or modify Diagnostic Tools 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 Diagnostic Tools resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.