Using aws-vault to manage access to your AWS resources from Kiro CLI

As we say at AWS, security is our top priority. This is why I have been spending time thinking about how to manage what our agentic AI tools can do. After publishing a previous post on this topic ( Getting Kiro CLI to use short lived AWS credentials ), this post takes a look at another approach you can take. Vincent reminded me about an awesome open source tool called aws-vault that helps developers move to using short lived, temporary credentials. In this post I wanted to compare and contrast approaches. But first, let me walk you through the setup. The documentation for aws-vault is good, and it has pretty much everything you need. That said, I did want to include in this post how I configured it to work with AWS Identity Centre, which is what I use. Setting things up Like timebound-iam, aws-vault is a tool that needs to be installed. Installation is painless, a quick "brew install aws-vault" and I was good to go. Also like timebound-iam, you need to associate aws-vault with credenti