Almost 6 months ago I wrote this post https://news.ycombinator.com/item?id=34038663 which was a big motivation to start building the IAM Policy Copilot.
We conducted a lot of interviews and honestly were confused about the best place to start. How can we best ingest data in order to generate a “least-privilege” policy. We started with integrating with Github actions to intercept traffic and generate the policies that can be used for deployments.
Our roadmap includes a multi-layered approach of analyzing data through traffic, static code and patterns/context in order to address more use-cases.
For now, we would love to learn from AWS partners and heavy AWS users how they currently deal with IAM and what an ideal solution would look like for them.
We conducted a lot of interviews and honestly were confused about the best place to start. How can we best ingest data in order to generate a “least-privilege” policy. We started with integrating with Github actions to intercept traffic and generate the policies that can be used for deployments.
Our roadmap includes a multi-layered approach of analyzing data through traffic, static code and patterns/context in order to address more use-cases.
For now, we would love to learn from AWS partners and heavy AWS users how they currently deal with IAM and what an ideal solution would look like for them.