AWS awscloudtrail documentation change
Summary
Removed mention of specific AWS interfaces (Console, CLI, API) from default permissions explanation
Security assessment
The change simplifies the description of default permissions but doesn't address any specific security vulnerability or weakness. It maintains the core security concept of requiring explicit IAM policies for access, just with less implementation detail about which interfaces are blocked.
Diff
diff --git a/awscloudtrail/latest/userguide/security_iam_id-based-policy-examples.md b/awscloudtrail/latest/userguide/security_iam_id-based-policy-examples.md index 5e1908da6..3857f7b71 100644 --- a//awscloudtrail/latest/userguide/security_iam_id-based-policy-examples.md +++ b//awscloudtrail/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesExample: Allowing and denying actions for a specified trail -By default, users and roles don't have permission to create or modify CloudTrail 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 CloudTrail resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.