iann0036/iamlive

Generate an IAM policy from AWS, Azure, or Google Cloud (GCP) calls using client-side monitoring (CSM) or embedded proxy

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 34 minutes ago
Added to GitGenius on September 20th, 2026
Created on February 4th, 2021
Open Issues & Pull Requests: 42 (+0)
GitHub issues: Enabled
Number of forks: 119
Total Stargazers: 3,408 (+0)
Total Subscribers: 20 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 681 days
Stale 30+ days: 9
Stale 90+ days: 9

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

iamlive is a policy generator that creates least-privilege IAM policies for AWS, Azure, or Google Cloud by monitoring API calls made during application execution.

The tool solves the problem of manually crafting minimal IAM policies by automatically capturing the actual cloud API calls your code makes and synthesizing them into a policy document. It operates in two modes: client-side monitoring (CSM) intercepts calls at the SDK level for AWS, while proxy mode works across all three providers by acting as an HTTP interceptor that sits between your application and the cloud APIs.

AWS users should choose this tool for straightforward policy generation from live workloads, particularly when using CSM mode which requires minimal setup. It suits development workflows where you run your application once and want to extract the exact permissions needed. Azure and Google Cloud support exists but is marked as preview and may produce incorrect outputs. The tool offers deployment flexibility through Lambda extensions, Docker containers, GitHub Actions integration, and LocalStack support, making it adaptable to different development environments.

The project shows consistent maintenance with regular updates addressing both core functionality and edge cases. Development activity includes ongoing refinement of the AWS mapping data that translates API calls to IAM actions, expansion of proxy mode capabilities across multiple cloud providers, and addition of configuration options that give users fine-grained control over policy generation behavior such as filtering failed calls only or forcing wildcard resources.