AWS AmazonElastiCache documentation change
Summary
Removed explicit mention of default denial for console/CLI/API access in IAM policy introduction
Security assessment
The edit simplifies policy explanation without altering security implications. While IAM policies are security-related, this change does not address vulnerabilities or add new security documentation - it removes redundant phrasing about default AWS permission behavior.
Diff
diff --git a/AmazonElastiCache/latest/dg/security_iam_id-based-policy-examples.md b/AmazonElastiCache/latest/dg/security_iam_id-based-policy-examples.md index ab2fc1761..477e883cb 100644 --- a//AmazonElastiCache/latest/dg/security_iam_id-based-policy-examples.md +++ b//AmazonElastiCache/latest/dg/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify ElastiCache 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 ElastiCache resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.