1 comment

[ 2.7 ms ] story [ 14.7 ms ] thread
Full disclosure: I'm one of the authors of the tool mentioned in the video, IAMbic.

The premise: Cloud IAM can get messy as your organization scales and you need to enforce compliance and security policies. Existing tools are often siloed and don’t give you a clear picture of your IAM state across different teams and platforms. IAMbic solves this problem by syncing your IAM state with version control, regardless of how you manage your IAM. It captures your IAM changes in Git as human-readable templates that you can track, review, and modify. If you just want to use IAMbic to gain visibility in your environment, you can stop here. But, you can also use IAMbic to apply changes to the cloud via Git workflows and prevent drift on selected resources, because these files in version control are bi-directional.

Right now, IAMbic supports AWS IAM (Users, groups, roles, policies), Identity Center, and Service Control Policies, Google Workspace IAM, Azure AD IAM, and Okta IAM. Our vision is to support other cloud providers, and give you a unified and flexible way to manage your cloud identities.

I'd love to hear your feedback on the approach.