AWS Security ChangesHomeSearch

AWS wickr documentation change

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

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

Summary

Removed detailed explanation about cross-account access requiring identity-based policies in trusted accounts, retaining only the cross-account reference link.

Security assessment

The change simplifies documentation by removing operational details but does not address or introduce concrete security vulnerabilities. The removed text clarified security configuration steps, but its absence doesn't directly indicate a security issue.

Diff

diff --git a/wickr/latest/adminguide-classic/security_iam_service-with-iam-resource-based-policies.md b/wickr/latest/adminguide-classic/security_iam_service-with-iam-resource-based-policies.md
index 74ef79b74..41a8b3c24 100644
--- a//wickr/latest/adminguide-classic/security_iam_service-with-iam-resource-based-policies.md
+++ b//wickr/latest/adminguide-classic/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_.