AWS aurora-dsql documentation change
Summary
Removed mention of default inability to use AWS Management Console, CLI, or API without explicit permissions
Security assessment
The change removes a redundant statement about default permissions but does not address a specific security vulnerability or weakness. The core IAM policy guidance remains unchanged, and there is no evidence this relates to patching a security issue.
Diff
diff --git a/aurora-dsql/latest/userguide/security_iam_id-based-policy-examples.md b/aurora-dsql/latest/userguide/security_iam_id-based-policy-examples.md index 6a9003125..1fb9be906 100644 --- a//aurora-dsql/latest/userguide/security_iam_id-based-policy-examples.md +++ b//aurora-dsql/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 Aurora DSQL 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 Aurora DSQL resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.