I needed cross-account access from one AWS account to another, and that meant having to set up AWSume.
While I have been using AWSume for some time, I have never set it up on my own. I could sense that it was going to be a challenge. As expected, there was lot of google searching, much frustration, and many chocolate bars (frustration serves as a great excuse to consume chocolate) involved throughout the process. I'm hoping this documentation will help me cut all that down the next time I have to install AWSume or any other packages using pipx.
python3 --versionpip3 --versionpython3 -m venv /path/to/myEnvsource myEnv/bin/activatebrew install pipxpipx ensurepathNow this is already more wordy than I had imagined and we've just completed getting the tools and venv ready. Next comes the fun part of configuring pipx.
By default, pipx installs packages in ~/.local/bin and creates virtual environments in ~/.local/pipx. To install AWSume in the created venv, these settings have to be changed. Luckily, they can be overriden with environment variables, PIPX_BIN_DIR and PIPX_HOME, respectively (see pipx documentation).
printevexport PIPX_BIN_DIR=~/myEnv/binexport PIPX_HOME=~/myEnvprintenvFinally - the long-awaited ultimate goal of this whole process - install AWSume.
pipx install awsumeTa-da! If the installation was successful, it'll return a message ending with:
done! ✨ 🌟 ✨
At this point, I will put down my pen. The remaining part of my story involves completing the rest of the AWSume setup and installing AWSume plugins. But I think it'd be best to point to the official documentation for the most accurate and up-to-date information.