AWS devops-guru documentation change
Summary
Simplified explanation of default permissions by removing redundant details about console/CLI/API access denial (which is implied by IAM policies)
Security assessment
The change removes explicit mention of access denial through specific interfaces but does not alter security recommendations or reveal new vulnerabilities. This is a documentation clarity improvement rather than a security-related update.
Diff
diff --git a/devops-guru/latest/userguide/security_iam_id-based-policy-examples.md b/devops-guru/latest/userguide/security_iam_id-based-policy-examples.md index ec722f0b1..be6823263 100644 --- a//devops-guru/latest/userguide/security_iam_id-based-policy-examples.md +++ b//devops-guru/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsA -By default, users and roles don't have permission to create or modify DevOps Guru 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 DevOps Guru resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.