AWS tnb documentation change
Summary
Removed redundant statement about default denial of AWS TNB actions via console/CLI/API. Clarifies that IAM policies are required to grant permissions for resource actions.
Security assessment
The change simplifies documentation about default IAM permissions but does not address a specific security vulnerability or weakness. It maintains existing security guidance about requiring explicit permissions through IAM policies.
Diff
diff --git a/tnb/latest/ug/security_iam_id-based-policy-examples.md b/tnb/latest/ug/security_iam_id-based-policy-examples.md index 94acf4938..810574ed1 100644 --- a//tnb/latest/ug/security_iam_id-based-policy-examples.md +++ b//tnb/latest/ug/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleService role policy examplesAllow users to -By default, users and roles don't have permission to create or modify AWS TNB 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 AWS TNB resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.