AWS AmazonCloudFront documentation change
Summary
Removed mention of default inability to use AWS Management Console/CLI/API without permissions, focusing explanation on resource modification permissions.
Security assessment
The change simplifies the explanation of default permissions but doesn't address any specific security vulnerability or weakness. It maintains the same security posture by emphasizing that users need explicit permissions through IAM policies.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/security_iam_id-based-policy-examples.md b/AmazonCloudFront/latest/DeveloperGuide/security_iam_id-based-policy-examples.md index 310c8dd41..1b7bf1b98 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/security_iam_id-based-policy-examples.md +++ b//AmazonCloudFront/latest/DeveloperGuide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesAllow users to view their own permissionsPermissions to acc -By default, users and roles don't have permission to create or modify CloudFront 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 CloudFront resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.