AWS AmazonECS documentation change
Summary
Simplified explanation of default permissions and removed references to specific AWS interfaces (Console/CLI/API). Added placeholder section with empty JSON and formatting marks.
Security assessment
The changes appear to be editorial improvements rather than security-related. The first edit simplifies the explanation of default permissions without changing security implications. The added JSON section contains no actual policy content or security guidance. There is no evidence of addressing vulnerabilities or security incidents.
Diff
diff --git a/AmazonECS/latest/developerguide/security_iam_id-based-policy-examples.md b/AmazonECS/latest/developerguide/security_iam_id-based-policy-examples.md index c5b79149a..43cb3843f 100644 --- a//AmazonECS/latest/developerguide/security_iam_id-based-policy-examples.md +++ b//AmazonECS/latest/developerguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Amazon ECS policy best practicesAllow Amazon ECS users to view their own permiss -By default, users and roles don't have permission to create or modify Amazon ECS 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 Amazon ECS resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. @@ -197,0 +198,6 @@ The following IAM policy can be attached to a user or group that would only allo +JSON + + +**** + +