AWS neptune-analytics documentation change
Summary
Removed mention of default inability to use AWS Management Console/CLI/API, focusing on IAM administrator's role in granting permissions.
Security assessment
The change simplifies the explanation of default permissions but does not introduce or address a specific security vulnerability. It clarifies IAM policy management without altering security recommendations or revealing new security features.
Diff
diff --git a/neptune-analytics/latest/userguide/security_iam_id-based-policy-examples.md b/neptune-analytics/latest/userguide/security_iam_id-based-policy-examples.md index 67a06bf6c..3bc43978d 100644 --- a//neptune-analytics/latest/userguide/security_iam_id-based-policy-examples.md +++ b//neptune-analytics/latest/userguide/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 Neptune Analytics 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 Neptune Analytics resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.