Our second release of IAM Zero!
Changelog
Our major focus this release was core usability features to make IAM Zero useful for developers in a day to day environment. We're not fully there yet - we aim to fix 27 and 28 in v0.3.0 which should make IAM Zero usable for AWS day-to-day to help you build least-privilege permissions.
Reworked policy editor
IAM Zero now groups permission issues recorded for the same token and policy together into a more convenient interface!
<img width="2032" alt="Screen Shot 2021-07-30 at 3 49 24 pm" src="https://user-images.githubusercontent.com/17420369/127634138-89e69cbb-d69d-4d98-a924-0ef25649da8d.png">
Support for multiple tokens
In v0.1.0, we only supported a single token (set as an environment variable). This has now been improved and we support multiple tokens to help you identify actions coming from different services or team members. Our v0.2.0 supports using DynamoDB and in-memory token stores (if you'd like support for a different storage backend please let us know in our [Slack](https://join.slack.com/t/commonfatecommunity/shared_invite/zt-q4m96ypu-_gYlRWD3k5rIsaSsqP7QMg)) and we aim to improve performance here in future releases by caching tokens in our event collection endpoint.
<img width="2032" alt="Screen Shot 2021-07-30 at 5 42 32 pm" src="https://user-images.githubusercontent.com/17420369/127635009-72ce2f42-1e4c-44c6-948e-c719ee9b93b2.png">
Initial support for hosting IAM Zero as a service
At Common Fate we are now running an internal deployment of IAM Zero hosted on AWS ECS. We're working on documentation to provide a deployment guide for IAM Zero. If you're interested in deploying IAM Zero to build least-privilege permissions in a team environment we'd love to hear from you so that we can best package IAM Zero as a CloudFormation deployment.