Jay Dhulia

Managing IAM across a large, fast-growing AWS footprint quickly outgrows manual review — every permission change creates friction for engineers and queue time for operators.

Building services on AWS necessitates using identity and access management (IAM) to define the privileges between cloud identities and resources. The policy language for IAM is as complex as it is expressive, often requiring extensive tooling to avoid pitfalls in large cloud environments.