I've been using Claude Code for managing my AWS infra and I have multiple accounts (probably should have just one but here we are), and everytime I needed to work with my Cloudfront or S3 or Dynamo or anything else I was constantly updating AWS IAM Policies and had to remember to remove the policy permissions after I was done so my account didn't just have access to everything for my user.
So I built a simple MCP server that talks to AWS STS and allows claude code to request temporary credentials with a standard AWS IAM policy scoped to the specific service and permissions for a limited amount of time.
Now claude asks me to approve the permissions and the MCP takes over and vends the credentials. The nice thing is that there is no backend to maintain or durations to manage since AWS STS handles all those including expiration of the credentials.
Check it out, give me your feedback and feature requests are welcome.
I've been using Claude Code for managing my AWS infra and I have multiple accounts (probably should have just one but here we are), and everytime I needed to work with my Cloudfront or S3 or Dynamo or anything else I was constantly updating AWS IAM Policies and had to remember to remove the policy permissions after I was done so my account didn't just have access to everything for my user.
So I built a simple MCP server that talks to AWS STS and allows claude code to request temporary credentials with a standard AWS IAM policy scoped to the specific service and permissions for a limited amount of time.
Now claude asks me to approve the permissions and the MCP takes over and vends the credentials. The nice thing is that there is no backend to maintain or durations to manage since AWS STS handles all those including expiration of the credentials.
Check it out, give me your feedback and feature requests are welcome.
Free & Open Source: https://github.com/builder-magic/timebound-iam