AWS ground-station documentation change
Summary
Removed specific references to AWS Management Console, CLI, and API in default permissions explanation. Simplified statement about granting permissions via IAM policies.
Security assessment
The change removes examples of access methods (console/CLI/API) but doesn't alter the core security policy guidance. This appears to be a clarification rather than addressing a specific vulnerability or weakness. IAM policy documentation is inherently security-related, but there's no evidence this change fixes a security issue or adds new security features.
Diff
diff --git a/ground-station/latest/ug/security_iam_id-based-policy-examples.md b/ground-station/latest/ug/security_iam_id-based-policy-examples.md index d1c07777c..9336fd4ea 100644 --- a//ground-station/latest/ug/security_iam_id-based-policy-examples.md +++ b//ground-station/latest/ug/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 AWS Ground Station 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 Ground Station resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.