Interview AWS

What is cross-account access, and how do you implement it securely with roles?

AWS · Advanced level

Answer

Cross-account access is usually implemented with a role in the target account, a trust policy for the source principal, least-privilege permissions, and STS AssumeRole temporary credentials. Conditions, MFA, external IDs, and CloudTrail improve security.

Technical explanation

A cross-account role has two sides: trust policy for who can assume it and permission policy for what it can do.

Multi-account governance should combine preventive controls such as SCPs with detective controls such as Config, GuardDuty, Inspector, Security Hub, CloudTrail, and Access Analyzer.

Central security, logging, and networking accounts reduce blast radius and protect evidence from workload account compromise.

Every control needs an owner, exception process, alert route, and remediation workflow or it becomes shelfware.

Hands-on example

1. Create a multi-account sandbox or use separate dev/security/logging accounts to test the control pattern.

2. Enable the relevant organization-level service or guardrail, then generate a controlled finding or denied action.

3. Route findings to Security Hub, EventBridge, ticketing, SIEM, or an incident channel with ownership metadata.

4. Document the exception process, remediation automation, and evidence required for audit.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More AWS interview questions

← All AWS questions