# Cross-account access

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Cross-account access lets a principal in one account use resources in another. In AWS it needs a permission on both sides. It is how organizations share data and run central tooling, and also how access spreads past the account boundary that teams assume is a limit.

## An example, sourced

AWS documents that you can allow a principal in one account to access resources in a second account, which is called cross-account access. The account where the principal exists is the trusted account and the account where the resource exists is the trusting account. To allow it, you attach a resource-based policy to the resource you want to share, and an identity-based policy to the identity that acts as the principal in the request.

## Why it matters here

Because both sides must agree, cross-account paths are easy to miss when a tool reads one account at a time. Ask whether a product models trust relationships across the organization. Review it as a path that crosses the organization, because a boundary drawn per account will not show the second half.

## Related pages

- [Third-party access: meaning and an example](/glossary/third-party-access/)
- [Cloud security intent enforcement: meaning and an example](/glossary/cloud-security-intent-enforcement/)
- [Policy simulation: meaning and an example](/glossary/policy-simulation/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic-cross-account.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://ciemtools.com/glossary/cross-account-access/
