AWS managed-blockchain documentation change
Summary
Removed redundant statement about default lack of permissions through AWS console/CLI/API while maintaining core message about requiring IAM policies for resource access
Security assessment
The change simplifies existing security documentation by removing redundant details about access methods (console/CLI/API) while preserving the core security principle of least privilege. No specific vulnerability or new security feature is addressed.
Diff
diff --git a/managed-blockchain/latest/ethereum-dev/security_iam_id-based-policy-examples.md b/managed-blockchain/latest/ethereum-dev/security_iam_id-based-policy-examples.md index 70a41bd9f..963166500 100644 --- a//managed-blockchain/latest/ethereum-dev/security_iam_id-based-policy-examples.md +++ b//managed-blockchain/latest/ethereum-dev/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsP -By default, users and roles don't have permission to create or modify AMB Access Ethereum 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 Access Ethereum resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.