Comment (0)

I sat down again, for about the eight billionth time, to install AWS’s CLI and get to work against some infrastructure. For at least the gazillionth time, I got a stupid error, that at this point I really feel the installation process ought to ignore, mitigate, or otherwise handle. But anyway, here’s one very common issue that keeps popping up over and over if you’ve got six installed already that isn’t the version that awscli wants (or doesn’t want).

The quick solution to this is to just tell pip to ignore the existing six installations.

pip install awscli --ignore-installed six --user<span id="mce_SELREST_start" style="overflow:hidden;line-height:0;"></span>

I did a quick search too, just to see what others had found and it looked like this wasn’t an entirely uncommon issue. On StackOverflow, there’s this same issue coming up with other installations.

I’d love to see this, and about a dozen other odd issues that always come up specifically with the awscli. The simple fix is for AWS just to go ahead and dig into how GCP builds gcloud because that CLI is easily the slickest option of the big three. But I digress, back to work on getting some infrastructure resources out there.

Comment (0)