AWS grafana documentation change
Summary
Simplified explanation of default permissions by removing redundant details about AWS Management Console/CLI/API access restrictions
Security assessment
The change removes a redundant statement about default lack of access through AWS interfaces, but does not address any specific security vulnerability or weakness. This is a documentation clarification rather than a security-related update.
Diff
diff --git a/grafana/latest/userguide/security_iam_id-based-policy-examples.md b/grafana/latest/userguide/security_iam_id-based-policy-examples.md index e2230bc1b..95b8a69e4 100644 --- a//grafana/latest/userguide/security_iam_id-based-policy-examples.md +++ b//grafana/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleSample policies for Amazon Managed Grafana -By default, users and roles don't have permission to create or modify Amazon Managed Grafana 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 Amazon Managed Grafana resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.