AWS healthimaging documentation change
Summary
Removed mention of specific AWS interfaces (Console, CLI, API) being restricted by default permissions, simplifying the explanation of default access controls.
Security assessment
The change removes redundant details about how default permissions apply to AWS interfaces but does not introduce new security policies or address a specific vulnerability. It maintains existing security guidance about IAM policies without altering security implications.
Diff
diff --git a/healthimaging/latest/devguide/security_iam_id-based-policy-examples.md b/healthimaging/latest/devguide/security_iam_id-based-policy-examples.md index 3ece2bdc9..9cfe48823 100644 --- a//healthimaging/latest/devguide/security_iam_id-based-policy-examples.md +++ b//healthimaging/latest/devguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify HealthImaging 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 HealthImaging resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.