AWS Security ChangesHomeSearch

AWS wickr documentation change

Service: wickr · 2025-10-22 · Documentation low

File: wickr/latest/adminguide/security_iam_service-with-iam-resource-based-policies.md

Summary

Simplified explanation about cross-account access requirements in resource-based policies by removing details about identity-based policy requirements in trusted accounts

Security assessment

The change removes explanatory text about cross-account policy requirements but does not address any specific security vulnerability. It clarifies documentation without altering security implications.

Diff

diff --git a/wickr/latest/adminguide/security_iam_service-with-iam-resource-based-policies.md b/wickr/latest/adminguide/security_iam_service-with-iam-resource-based-policies.md
index 5acfef418..3f6d999bd 100644
--- a//wickr/latest/adminguide/security_iam_service-with-iam-resource-based-policies.md
+++ b//wickr/latest/adminguide/security_iam_service-with-iam-resource-based-policies.md
@@ -13 +13 @@ Resource-based policies are JSON policy documents that you attach to a resource.
-To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. Adding a cross-account principal to a resource-based policy is only half of establishing the trust relationship. When the principal and the resource are in different AWS accounts, an IAM administrator in the trusted account must also grant the principal entity (user or role) permission to access the resource. They grant permission by attaching an identity-based policy to the entity. However, if a resource-based policy grants access to a principal in the same account, no additional identity-based policy is required. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the _IAM User Guide_.
+To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the _IAM User Guide_.