Aws cli v2 installs it's own self contained python so it shouldn't be tied to any system install. Frankly it's good to see devs not ceding to the internet rage

Aws cli v2 installs it's own self contained python so it shouldn't be tied to any system install. Frankly it's good to see devs not ceding to the internet rage mob. I remember before aws hired the main guy behind boto and I had to install 10 different tar.gz tools from 10 different aws teams and install all of them and setup 20 different env variables. Running their installer isn't difficult and I've included it in our docker and ami builds easily. If you want a fixed version, download whatever from their repo and mirror it to your internal storage and you can always install from there and ensure you're running the exact version you like. This response (from a year ago) seems perfectly reasonable and explains in detail a good number of reasons why they aren't using pip: https://github.com/aws/aws-cli/issues/4947#issuecomment-586046886 https://github.com/aws/aws-cli/issues/4947#issuecomment-5860...