149

I recently noticed that I am running an old version of AWS CLI that is lacking some functionality I need:

$aws --version
aws-cli/1.2.9 Python/3.4.3 Linux/3.13.0-85-generic

How can I upgrade to the latest version of the AWS CLI (1.10.24)?

Edit:

Running the following command fails to update AWS CLI:

$ pip install --upgrade awscli
Requirement already up-to-date: awscli in /usr/local/lib/python2.7/dist-packages
Cleaning up...

Checking the version:

$ aws --version
aws-cli/1.2.9 Python/3.4.3 Linux/3.13.0-85-generic
Borealis
  • 6,553
  • 12
  • 58
  • 104
  • 1
    I had this same situation and was caused by the aws cli being originally installed via `apt-get install awscli`. Solution was to remove it first (`apt-get remove awscli`) and follow `pip install` answers below. – Darren Reid Dec 15 '17 at 01:50
  • I did (apt-get remove awscli) but then after following (pip install...) commands I can't find the awscli executable. The output of (pip install ...) says successfully installed. – NKM Oct 26 '18 at 04:50
  • If I don't use "--user" option in pip install then I could find awscli executable under /usr/local/bin (I am on Debian Jessie). But with --user option the exec is not available in ~/.local or in any of the python installation package folders (dist-package or site-package). – NKM Oct 26 '18 at 07:46

13 Answers13

120

From http://docs.aws.amazon.com/cli/latest/userguide/installing.html#install-with-pip

To upgrade an existing AWS CLI installation, use the --upgrade option:

pip install --upgrade awscli
David Arenburg
  • 87,271
  • 15
  • 123
  • 181
Vijay Dev
  • 24,306
  • 20
  • 73
  • 96
  • I get the following message: `Requirement already up-to-date: awscli in /usr/local/lib/python2.7/dist-packages`. Although when I run `aws --version`, I get `aws-cli/1.2.9 Python/3.4.3 Linux/3.13.0-85-generic`. – Borealis May 01 '16 at 17:10
  • 23
    Try pip3 install --upgrade awscli – RaviTezu May 01 '16 at 17:25
  • 13
    Running `sudo pip3 install --upgrade awscli` and a reboot did the trick. Thanks for the help. – Borealis May 01 '16 at 19:27
  • 19
    Just a reboot is required after installing aws cli. – JoeTidee Sep 13 '16 at 09:33
  • 4
    I can't believe a reboot is *required*, but in this case it was faster to reboot my vm than find an alternative [that 'reboot voodoo' is for windows]. – toddkaufmann Oct 02 '16 at 17:13
  • If PyYAML failed you while installing: `pip uninstall awscli`, then `sudo apt-get install python-dev` and `pip install awscli` again. – zed Jan 09 '18 at 13:49
  • For me helped going `sudo su` first. – Remigiusz Jun 07 '19 at 06:09
  • you don't need to reboot, just enter to another terminal, or restart the current one – Kostanos Jul 24 '19 at 15:28
  • I now have aws and aws2 in my systems. How do I get rid of aws and rename my aws2 as aws? – Ankur Bhatia Jun 18 '20 at 12:47
  • Instead of reboot or starting another shell, you can run "hash -r" to clear the remembered utility locations. Or "hash aws" to reset just the remembered aws executable location. – Peter Wiseman Mar 11 '21 at 03:01
51

On Linux and MacOS X, here are the three commands that correspond to each step:

$ curl "https://s3.amazonaws.com/aws-cli/awscli-bundle.zip" -o "awscli-bundle.zip"
$ unzip awscli-bundle.zip
$ sudo ./awscli-bundle/install -i /usr/local/aws -b /usr/local/bin/aws
Andong Zhan
  • 8,732
  • 4
  • 21
  • 22
  • 3
    updating via `pip` did not work for me - deleting `aws` and re-installing it this way did work. – B M Oct 08 '17 at 22:12
  • 1
    You saved my day. AWS is getting poor on its documentation. – Kannaiyan Dec 16 '18 at 00:07
  • this option worked for me as I needed to upgrade `/usr/local/aws` ( not `/home/ubuntu/.local/bin/aws` ) to be used by *jenkins* user – hit3k Aug 29 '19 at 05:53
  • The documentation of AWS is indeed deteriorating rapidly. This is the correct answer, I can't understand why the questioner accepted an answer which they'd clearly stated in their edit didn't work - the pip packages are often behind the current latest which is a problem when using new stuff like EKS. Note: I had to exit the shell and log back in for the aws command to pick up the new version. No idea why. – Dick Chesterwood Jan 09 '20 at 17:39
24

This does not work:

pip install --upgrade awscli

This worked fine on Ubuntu 14.04( no need to reboot also .. You would have to first install pip3 ):

pip3 install --upgrade awscli

Deepak Singhal
  • 9,577
  • 10
  • 50
  • 92
  • 4
    This may require: `apt-get install python3-pip` Either command works equally well for me on Ubuntu 14.04. – dannyman Jul 07 '17 at 22:17
13

For Ubuntu 16.04 I used parts of the other answers and comments and just reloaded bash instead of rebooting.

I installed the aws-cli using apt so I removed that first:

sudo apt-get remove awscli

Then I could pip install (I chose to use sudo to install globally with pip2):

sudo pip install -U awscli

Since I was doing this on a server I didn't want to reboot it, but reloading bash did the trick:

source ~/.bashrc

At this point I could use the new version of aws cli

aws --version
petroleyum
  • 648
  • 1
  • 5
  • 11
8

Try sudo pip install --upgrade awscli, and open a new shell. This worked well for me (no need to reboot).

Hadi Pouransari
  • 89
  • 1
  • 1
  • On Mac OS, I had to run `sudo pip install --upgrade awscli` for my machine to be able to uninstall the previous version of the awscli (after the initial upgrade ran successfully) – Lynn Langit Dec 30 '17 at 02:33
4

Simple use sudo pip install awscli --force-reinstall --upgrade

This will upgrade all the required modules.

Kc Bickey
  • 761
  • 7
  • 11
  • on my jenkins machine I didn't want to explicitly uninstall the cli, so I used this method and worked like a charm! – URB Jun 28 '20 at 20:25
4

Update: Upgrade instance using AWS CLI v1 to AWS CLI v2:

This question and answer was initially created when there was only an AWS CLI v1. There is now a AWS CLI v2. The installation instructions for the AWS CLI v2 can be found here.

The new AWS CLI v2 has different installation instructions based on whether your EC2 instance is using Linux x86 (64-bit) or Linux ARM architecture.

To upgrade to AWS CLI v2, on an EC2 instance using Linux ARM, I had to issue the following commands:

rm -rf /bin/aws
curl "https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
./aws/install -i /usr/local/aws -b /bin

Subsequently test your AWS CLI version by executing: aws --version

For the Linux x86 (64-bit) architecture I'm hoping the commands are the same except for replacing the curl command with the following: (as per the installation instructions)

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"

The AMI I used was the most recent one currently available and it was still using the AWS CLI v1. In the future if AWS starts packaging AWS CLI v2 with their AMIs this answer might require an update.

Original answer: Upgrade instance using AWS CLI v1 to use the most recent version of AWS CLI v1:

If you are having trouble installing the AWS CLI using pip you can use the "Bundled Installer" as documented here.

The steps discussed there are as follows:

$ curl "https://s3.amazonaws.com/aws-cli/awscli-bundle.zip" -o "awscli-bundle.zip"
$ unzip awscli-bundle.zip
$ sudo ./awscli-bundle/install -i /usr/local/aws -b /usr/local/bin/aws

Check your AWS CLI version subsequently as a sanity-check that everything executed correctly:

$ aws --version

If the AWS CLI didn't update to the latest version as expected maybe the AWS CLI binaries are located somewhere else as the previously-given commands assume.

Determine where AWS CLI is being executed from:

$ which aws

In my case, AWS CLI was being executed from /bin/aws, so I had to install the "Bundled Installer" using that location as follows:

$ sudo ./awscli-bundle/install -i /user/local/aws -b /bin/aws
CloudNinja
  • 1,346
  • 1
  • 17
  • 30
  • using the bundled installer somehow makes the resulting docker image LARGER than using pip ... mind blowing – Chad Grant Dec 26 '19 at 23:37
  • It may be necessary to open a new shell after installing - for some reason "aws" doesn't point to the new install until exiting and restarting. – Dick Chesterwood Jan 09 '20 at 17:37
4

On Mac you can use homebrew:

to install: brew install awscli

to upgrade: brew upgrade awscli

Make sure you don't have multiple installations: where aws

Daniel
  • 2,527
  • 1
  • 16
  • 18
2
pip install awscli --upgrade --user

The --upgrade option tells pip to upgrade any requirements that are already installed. The --user option tells pip to install the program to a subdirectory of your user directory to avoid modifying libraries used by your operating system.

Semir Hodzic
  • 269
  • 3
  • 7
0

We can follow the below commands to install AWS CLI on UBUNTU:

sudo apt install curl

curl “https://s3.amazonaws.com/aws-cli/awscli-bundle.zip” -o “awscli-bundle.zip”

unzip awscli-bundle.zip

sudo ./awscli-bundle/install -i /usr/local/ aws -b /usr/local/bin/aws

rm -rf awscli-bundle.zip awscli-bundle

To test: aws — version

For More Info :

https://gurudathbn.wordpress.com/2018/03/31/installing-aws-cli-on-ubuntu/

Gurudath BN
  • 1,242
  • 19
  • 21
0

When using sudo pip install --upgrade awscli I got the following error:

ERROR: Could not install packages due to an EnvironmentError: [Errno 30] Read-only file system: '/lib'

By using sudo with -H option, I could fix the problem.

sudo -H pip install --upgrade awscli
Stefan Rode
  • 61
  • 1
  • 3
0

Currently, using pip will get you the old version of awscli, 1.18.103.

The latest version of aws-cli, 2.0.33 is on the v2 branch. You can download the installer for Linux, Windows and macOS from here.

Ben Butterworth
  • 6,030
  • 1
  • 28
  • 48
-1

Try AWS Cloud Shell, Quick and easy

AWS CloudShell is a browser-based shell that makes it easy to securely manage, explore, and interact with your AWS resources. CloudShell is pre-authenticated with your console credentials.

Benefits

  • No extra credentials to manage
  • Always up to date
  • No cost

More Details here https://aws.amazon.com/cloudshell/

  • Customizable
Rahul
  • 144
  • 1
  • 8
  • Until unless used for a specific purpose, common day to day operations could easily be handled with Cloud shell – Rahul Mar 10 '21 at 05:35