Q: What is cross-account IAM role assumption, and why is it considered safer than creating IAM users in every account?
If you have 10 AWS accounts (Dev, QA, Prod for various products), creating 10 individual IAM Users for an engineer means 10 sets of permanent access keys to manage, rotate, and potentially leak.
Master cloud-native security and container runtime defense: Prepare with KodeKloud's CKS course with live browser-based terminal sandboxes.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Least-privilege access, encrypted secrets in transit/at rest, and continuous vulnerability scanning are foundational. The interviewer is testing: STS AssumeRole, centralized identity management, reducing attack surface.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
If you have 10 AWS accounts (Dev, QA, Prod for various products), creating 10 individual IAM Users for an engineer means 10 sets of permanent access keys to manage, rotate, and potentially leak.
- The engineer has a single IAM User (or SSO identity) exclusively in a central "Identity Account".
- In the "Prod Account", an IAM Role is created that trusts the Identity Account.
- The engineer uses the AWS CLI/Console to run
AssumeRole. AWS STS issues temporary, short-lived (e.g., 1 hour) credentials to act as that Role in the Prod Account.
Remediation & Permanent Safeguards
A safer architecture is a Hub and Spoke model using sts:AssumeRole. This inherently forces credential expiration and allows security teams to manage all identities from a single pane of glass.
- The engineer has a single IAM User (or SSO identity) exclusively in a central "Identity Account".
- In the "Prod Account", an IAM Role is created that trusts the Identity Account.
- The engineer uses the AWS CLI/Console to run AssumeRole. AWS STS issues temporary, short-lived (e...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Revoking compromised credentials immediately without analyzing forensic audit trails for active exploitation when configuring Security cross account Deactivating a compromised access key prevents abuse while preserving forensic identity for CloudTrail investigations to assess blast radius.
- Terminating compromised instances immediately during incident triage without isolating volatile RAM state when configuring Security cross account Terminating compromised instances immediately destroys volatile memory evidence (RAM dumps) required to establish intrusion timelines.
-
Injecting plaintext secrets into container environment variables rather than fetching from dynamic secret vaults when configuring Security cross account
Container environment variables are visible via
docker inspector Kubernetes API queries, leaking sensitive API tokens to developers. - Failing to enforce automated credential rotation for third-party SaaS integration tokens when configuring Security cross account Static long-lived API tokens shared across internal services represent the highest-probability vector for supply-chain credential compromise.