Laura Reith

Most AWS workforce access hinges on a single Region and a single identity provider. When either one goes down, everyone who signs in is affected—developers can't ship, DevOps engineers can't deploy, and administrators may be locked out just when they need access most.

As organizations grow across teams, AWS accounts, and countries, workforce access often becomes a bottleneck. This is especially true when you depend on existing IAM roles you don't want to re-engineer.

Here we explore the lessons learned where customers have acquired more than one AWS organizations through acquisitions or conversely, customers who have divested a part of their business.

AWS trusted identity propagation simplifies data access management in large organizations by seamlessly integrating with enterprise identity providers like Okta and Azure AD.

In this workshop, learn how to create a data perimeter by building controls that allow access to data only from expected network locations and by trusted identities. The workshop consists of five modules, each designed to illustrate a different AWS Identity and Access Management (IAM) principle or network control.