aws-tools
iamlive
| aws-tools | iamlive | |
|---|---|---|
| 1 | 30 | |
| 1 | 2,961 | |
| - | - | |
| 4.4 | 6.2 | |
| almost 3 years ago | 3 months ago | |
| Go | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aws-tools
-
How newcomers can avoid and prevent unwanted charges on their AWS accounts
Just recently I have decide to open source it and make it available in the Serverless Application Repository. To start using it you just need to deploy it into your account, feel free to propose new features or open a new issue if you find any in the github repository.
iamlive
-
Why has AWS made IAM Actions impossible to find?
Also things like this (same guy) if you have a sandbox to play in with wider permissions and are trying to build a more scoped profile: https://github.com/iann0036/iamlive
- iann0036/iamlive: Generate an IAM policy from AWS calls using client-side monitoring (CSM) or embedded proxy
-
Why Companies Still Struggle with Least Privilege in the Cloud?
I know there is a tool called iamlive that logs all API calls on your local machine. So you can run commands as an admin user locally while this is running, and find out what permissions were needed. Then you tear down the infra you just deployed, and add those same permissions to a service user of some kind (e.g. a CICD role) to avoid over-privileging it. It's messy but it can be helpful.
-
AWS Creates New Policy-Based Access Control Language Cedar
actually Ian (aws hero) has a tool that does exactly this
https://github.com/iann0036/iamlive
- Permissions Map
- iamlive
-
Show HN: Slauth.io (YC S22) – IAM Policy Auto-Generation
I have used https://github.com/iann0036/iamlive with great success in the past. On high level, the approach you are describing is iamlive on steroids and UX improved.
Kudos on launch, will check your beta
- IAM Live
-
Pike: Tool to determine your IAM requirements from code
Thanks! Permissions are determined per resource or datasource. There's no easy way that I had found, especially if you want this done statically, https://github.com/iann0036/iamlive does it by inspecting your api calls but there's always a look up somewhere. Hopefully ill manage to get a few community contributions and get the ball rolling, i've made it as easy as I could to add support for other resources without you even really having to know golang.
-
The End of CI
IAM isn’t fun, but there’s lots of options.
https://pypi.org/project/access-undenied-aws/ will allow you to start with least privilege and fix specific issues.
https://github.com/iann0036/iamlive allows an admin to perform the action via CLI and capture the policy.
Access advisor can inspect how you actually use the role and give suggestions on what to remove.
A more helpful suggestion is to experiment with these tools and then find gaps in IAM actions and submit those as feature requests via your TAM.
What are some alternatives?
git-secrets - Prevents you from committing secrets and credentials into git repositories
aws-leastprivilege - Generates an IAM policy for the CloudFormation service role that adheres to least privilege.
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
consoleme - A Central Control Plane for AWS Permissions and Access
policy_sentry - IAM Least Privilege Policy Generator
iamzero - Identity & Access Management simplified and secure.
iamlive-lambda-extension - Lambda Extension for iamlive
trailscraper - A command-line tool to get valuable information out of AWS CloudTrail
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
Jenkins - Jenkins automation server
gitlab-ci-local - Tired of pushing to test your .gitlab-ci.yml?