AWS managed-blockchain documentation change
Summary
Removed mention of specific AWS interfaces (Management Console, CLI, API) in the explanation of default permissions for AMB Query resources. Simplified the phrasing about granting permissions via IAM policies.
Security assessment
The change clarifies default permissions but does not address a specific security vulnerability or weakness. It removes redundant details about access methods without altering the security posture or introducing new security features.
Diff
diff --git a/managed-blockchain/latest/ambq-dg/security_iam_id-based-policy-examples.md b/managed-blockchain/latest/ambq-dg/security_iam_id-based-policy-examples.md index a37b60f6e..4dac09ef6 100644 --- a//managed-blockchain/latest/ambq-dg/security_iam_id-based-policy-examples.md +++ b//managed-blockchain/latest/ambq-dg/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesAllow users to view their own permissions Accessing AMB Que -By default, users and roles don't have permission to create or modify AMB Query 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 AMB Query resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.