They are leveraging the Cross-Account access feature of the AWS Management console, which has been released early this year: <a href="https:&#x2F;&#x2F;aws.amazon.com&#x2F;blogs&#x2F;aws&#x2F;new-cross-account-access-in-the-aws-management-console&#x2F;" rel="nofollow">https:&#x2F;&#x2F;aws.amazon.com&#x2F;blogs&#x2F;aws&#x2F;new-cross-account-access-in...</a><p>&gt; If you switch to ops-admin @ stage for example, and then go to the S3 page in the console,<p>&gt; will you get a listing of all buckets in the stage AWS account even though your login<p>&gt; session as calvin &quot;belongs&quot; to an other AWS account (segment)?<p>It should work like that, yes.
Your privileges will be &quot;scoped&quot; to the role you are assuming in the &quot;stage&quot; account.<p>&gt; I can see how having separate AWS accounts for dev&#x2F;stage&#x2F;prod makes things easier.<p>It&#x27;s also a good way of maintaining agility when you have multiple teams working in parallel on different projects (ex: 1 team = 1 AWS account).
Zalando has recently published a bunch of tools leveraging IAM to help manage multiple AWS accounts (ex: federated SSH access)  : <a href="https:&#x2F;&#x2F;stups.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;stups.io&#x2F;</a>