Classicops

Hi, I am a devops engineer and I have seen people facing troubles giving access to their AWS Accounts, especially when they are production accounts. What ends up happening is people give access that is too permissive which is perpetual in nature or its too restrictive (still perpetual). There is back and forth over communication tools like slack and JIRA. The permissions last as long as the person works with the AWS account owner. I looked around for tools that would be solving this problem, but I really couldn't find one. I decided to build a tool wherein users who want access to the AWS Account could request for permissions by either using a managed IAM Policy or providing a custom IAM policy for a given time period. Once the access is approved, he would be allowed access to AWS using the console or using CLI credentials. Once the time period is over the access would be revoked automatically. I understand there would be concerns around giving IAM access to external softwares so we do plan for certifications and also provide options for a self hosted offering.