AWS wickr documentation change
Summary
Simplified explanation of resource-based policies by removing redundant details about policy definitions and conditions
Security assessment
Change removes explanatory text about policy structure but does not alter security guidance. No evidence of addressing vulnerabilities or modifying security controls.
Diff
diff --git a/wickr/latest/adminguide-classic/security_iam_access-manage-resource-based-policies.md b/wickr/latest/adminguide-classic/security_iam_access-manage-resource-based-policies.md index 05fe1c9de..d60491537 100644 --- a//wickr/latest/adminguide-classic/security_iam_access-manage-resource-based-policies.md +++ b//wickr/latest/adminguide-classic/security_iam_access-manage-resource-based-policies.md @@ -9 +9 @@ This guide documents the classic version of the AWS Wickr administration console -Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM _role trust policies_ and Amazon S3 _bucket policies_. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services. +Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM _role trust policies_ and Amazon S3 _bucket policies_. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy.