Cross-Account Access Fundamentals
You'll learn: Why organizations need resources and identities from one cloud account to securely access resources in another, and the architectural patterns that make it work.
Why Cross-Account Access?
Imagine your organization has separate cloud accounts for development, staging, and production—or different business units each have their own account. Eventually, a service in the dev account needs to read data from the prod account, or a central logging system needs to collect logs from all accounts.
Cross-account access enables identities (users, roles, services) in one cloud account to interact with resources in a different account, without duplicating credentials or creating backdoors.
Common Use Cases
- Multi-environment architectures: Dev/test/prod separation for blast radius containment
- Centralized services: A single security account auditing or managing resources across dozens of accounts
- Partner/vendor access: Granting third-party systems limited access without creating users in your account
- Organizational boundaries: Different departments or subsidiaries operating independently but needing occasional integration
Architectural Patterns
The primary mechanism uses assumable roles combined with trust relationships. The target account creates a role and defines a trust policy that says "Account B can assume this role." Account B then uses temporary credentials (via AssumeRole) to access resources in the target account—no passwords or long-term keys cross boundaries.
This maintains the least privilege principle since you grant only specific permissions for specific cross-account scenarios, and all access creates audit trails showing which account accessed what.
Key Takeaway: Cross-account access enables secure, auditable resource sharing between cloud accounts using temporary credentials and trust relationships, supporting multi-account strategies that isolate environments while enabling controlled integration.