Topics

• AWS CLI install and update instructions

• Troubleshooting AWS CLI install and uninstall errors

• Next steps

$sudo yum remove awscli

You can install the AWS CLI by using one of the following methods:

Command line installer - Linux x86 (64-bit)

To update your current installation of AWS CLI, download a new installer each time you update to overwrite previous versions. Follow these steps from the command line to install the AWS CLI on Linux.

The following are quick installation steps in a single copy and paste group that provide a basic installation. For guided instructions, see the steps that follow.

Note

(Optional) The following command block downloads and installs the AWS CLI without first verifying the integrity of your download. To verify the integrity of your download, use the below step by step instructions.

To install the AWS CLI, run the following commands.

$curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"unzip awscliv2.zipsudo ./aws/install

To update your current installation of the AWS CLI, add your existing symlink and installer information to construct theinstall command using the--bin-dir,--install-dir, and--update parameters. The following command block uses an example symlink of/usr/local/bin and example installer location of/usr/local/aws-cli to install the AWS CLI locally for the current user.

$curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"unzip awscliv2.zipsudo ./aws/install --bin-dir/usr/local/bin --install-dir/usr/local/aws-cli --update

Guided installation steps

1. Download the installation file in one of the following ways:

   • Use thecurl command – The-o option specifies the file name that the downloaded package is written to. The options on the following example command write the downloaded file to the current directory with the local nameawscliv2.zip.

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

   • Downloading from the URL – To download the installer with your browser, use the following URL:https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip

2. (Optional) Verifying the integrity of your downloaded zip file

   If you chose to manually download the AWS CLI installer package.zip in the above steps, you can use the following steps to verify the signatures by using theGnuPG tool.

   The AWS CLI installer package.zip files are cryptographically signed using PGP signatures. If there is any damage or alteration of the files, this verification fails and you should not proceed with installation.

   1. Download and install thegpg command using your package manager. For more information aboutGnuPG, see theGnuPG website.

   2. To create the public key file, create a text file and paste in the following text.

      -----BEGIN PGP PUBLIC KEY BLOCK-----mQINBF2Cr7UBEADJZHcgusOJl7ENSyumXh85z0TRV0xJorM2B/JL0kHOyigQluUGZMLhENaG0bYatdrKP+3H91lvK050pXwnO/R7fB/FSTouki4ciIx5OuLlnJZIxSzxPqGl0mkxImLNbGWoi6Lto0LYxqHN2iQtzlwTVmq9733zd3XfcXrZ3+LblHAgEt5GTfNxEKJ8soPLyWmwDH6HWCnjZ/aIQRBTIQ05uVeEoYxSh6wOai7ss/KveoSNBbYzgbdzoqI2Y8cgH2nbfgp3DSasaLZEdCSsIsK1u05CinE7k2qZ7KgKAUIcT/cR/grkC6VwsnDU0OUCideXcQ8WeHutqvgZH1JgKDbznoIzeQHJD238GEu+eKhRHcz8/jeG94zkcgJOz3KbZGYMiTh277Fvj9zzvZsbMBCedV1BTg3TqgvdX4bdkhf5cH+7NtWOlrFj6UwAsGukBTAOxC0l/dnSmZhJ7Z1KmEWilro/gOrjtOxqRQutlIqG22TaqoPGfYVN+en3Zwbt97kcgZDwqbuykNt64oZWc4XKCa3mprEGC3IbJTBFqglXmZ7l9ywGEEUJYOlb2XrSuPWml39beWdKM8kzr1OjnlOm6+lpTRCBfo0wa9F8YZRhHPAkwKkXXDeOGpWRj4ohOx0d2GWkyV5xyN14p2tQOCdOODmz80yUTgRpPVQUtOEhXQARAQABtCFBV1MgQ0xJIFRlYW0gPGF3cy1jbGlAYW1hem9uLmNvbT6JAlQEEwEIAD4CGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AWIQT7Xbd/1cEYuAURraimMQrMRnJHXAUCaGveYQUJDMpiLAAKCRCmMQrMRnJHXKBYD/9Ab0qQdGiO5hObchG8xh8Rpb4Mjyf60JrVo6m8GNjNj6BHkSc8fuTQJ/FaEhaQxj3pjZ3GXPrXjIIVChmICLlFuRXYzrXcPw0lniybypsZEVai5kO0tCNBCCFuMN9RsmmRG8mf7lC4FSTbUDmxG/QlYK+0IV/luJkzxWa+rySkdpm0JdqumjegNRgObdXHAQDWlubWQHWyZyIQ2B4U7AxqSpcdJp6IS4Zds4wVLd1WE5pquYQ8vS2cNlDm4QNg8wTj58e3lKN47hXHMIb6CHxRnb947oJapg189LLPR5koh+EorNkA1wu5mAJtJvy5YMsppy2y/kIjp3lyY6AmPT1posgGk70ZCmToEZ5rbd7ARExtlh76A0cabMDFlEHDIK8RNUOSRr7L64+KxOUegKBfQHb9dADYqqiKqpCbKgvtWlds909Ms74JBgr2KwZCSY1HaOxnIr4CY43QRqAq5YHOay/mU+6whhmdF18vpyK0vfkvvGresWtSXbag7Hkt3XjaEw76BzxQH21EBDqU8WJVjHgU6ru+DJTs+SxgJbaT3hb/vyjlw0lK+hFfhWKRwgOXH8vqducF95NRSUxtS4fpqxWVaw3QV2OWSjbne99A5EPEySzryFTKbMGwaTlAwMCwYevt4YT6eb7NmFhTx0Fis4TalUs+j+c7Kg92pDx2uQ===OBAt-----END PGP PUBLIC KEY BLOCK-----

      For reference, the following are the details of the public key.

      Key ID:           A6310ACC4672475CType:             RSASize:             4096/4096Created:          2019-09-18Expires:          2026-07-07User ID:          AWS CLI Team <aws-cli@amazon.com>Key fingerprint:  FB5D B77F D5C1 18B8 0511  ADA8 A631 0ACC 4672 475C

   3. Import the AWS CLI public key with the following command, substitutingpublic-key-file-name with the file name of the public key you created.

      $gpg --importpublic-key-file-namegpg: /home/username/.gnupg/trustdb.gpg: trustdb createdgpg: key A6310ACC4672475C: public key "AWS CLI Team <aws-cli@amazon.com>" importedgpg: Total number processed: 1gpg:               imported: 1

   4. Download the AWS CLI signature file for the package you downloaded. It has the same path and name as the.zip file it corresponds to, but has the extension.sig. In the following examples, we save it to the current directory as a file namedawscliv2.sig.

      For the latest version of the AWS CLI, use the following command block:

      $curl -o awscliv2.sighttps://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip.sig

   5. Verify the signature, passing both the downloaded.sig and.zip file names as parameters to thegpg command.

      $gpg --verify awscliv2.sig awscliv2.zip

      The output should look similar to the following.

      gpg: Signature made Mon Nov  4 19:00:01 2019 PSTgpg:                using RSA key FB5D B77F D5C1 18B8 0511 ADA8 A631 0ACC 4672 475Cgpg: Good signature from "AWS CLI Team <aws-cli@amazon.com>" [unknown]gpg: WARNING: This key is not certified with a trusted signature!gpg:          There is no indication that the signature belongs to the owner.Primary key fingerprint: FB5D B77F D5C1 18B8 0511  ADA8 A631 0ACC 4672 475C

      Important

      The warning in the output is expected and doesn't indicate a problem. It occurs because there isn't a chain of trust between your personal PGP key (if you have one) and the AWS CLI PGP key. For more information, seeWeb of trust.

3. Unzip the installer. If your Linux distribution doesn't have a built-inunzip command, use an equivalent to unzip it. The following example command unzips the package and creates a directory namedaws under the current directory.

   $unzip awscliv2.zip

   Note

   When updating from a previous version, theunzip command prompts to overwrite existing files. To skip these prompts, such as with script automation, use the-u update flag forunzip. This flag automatically updates existing files and creates new ones as needed.

   $unzip -u awscliv2.zip

4. Run the install program. The installation command uses a file namedinstall in the newly unzippedaws directory. By default, the files are all installed to/usr/local/aws-cli, and a symbolic link is created in/usr/local/bin. The command includessudo to grant write permissions to those directories.

   $sudo ./aws/install

   You can install withoutsudo if you specify directories that you already have write permissions to. Use the following instructions for theinstall command to specify the installation location:

   • Ensure that the paths you provide to the-i and-b parameters contain no volume name or directory names that contain any space characters or other white space characters. If there is a space, the installation fails.

   • --install-dir or-i – This option specifies the directory to copy all of the files to.

     The default value is/usr/local/aws-cli.

   • --bin-dir or-b – This option specifies that the mainaws program in the install directory is symbolically linked to the fileaws in the specified path. You must have write permissions to the specified directory. Creating a symlink to a directory that is already in your path eliminates the need to add the install directory to the user's$PATH variable.

     The default value is/usr/local/bin.

   $./aws/install -i/usr/local/aws-cli -b/usr/local/bin

   Note

   To update your current installation of the AWS CLI, add your existing symlink and installer information to construct theinstall command with the--update parameter.

   $sudo ./aws/install --bin-dir/usr/local/bin --install-dir/usr/local/aws-cli --update

   To locate the existing symlink and installation directory, use the following steps:

   1. Use thewhich command to find your symlink. This gives you the path to use with the--bin-dir parameter.

      $which aws/usr/local/bin/aws

   2. Use thels command to find the directory that your symlink points to. This gives you the path to use with the--install-dir parameter.

      $ls -l /usr/local/bin/awslrwxrwxrwx 1 ec2-user ec2-user 49 Oct 22 09:49 /usr/local/bin/aws ->/usr/local/aws-cli/v2/current/bin/aws

5. Confirm the installation with the following command.

   $aws --versionaws-cli/2.27.41 Python/3.11.6 Linux/5.10.205-195.807.amzn2.x86_64

   If theaws command cannot be found, you might need to restart your terminal or follow the troubleshooting inTroubleshooting errors for the AWS CLI.

Command line - Linux ARM

To update your current installation of AWS CLI, download a new installer each time you update to overwrite previous versions. Follow these steps from the command line to install the AWS CLI on Linux.

The following are quick installation steps in a single copy and paste group that provide a basic installation. For guided instructions, see the steps that follow.

Note

(Optional) The following command block downloads and installs the AWS CLI without first verifying the integrity of your download. To verify the integrity of your download, use the below step by step instructions.

To install the AWS CLI, run the following commands.

$curl "https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip" -o "awscliv2.zip"unzip awscliv2.zipsudo ./aws/install

To update your current installation of the AWS CLI, add your existing symlink and installer information to construct theinstall command using the--bin-dir,--install-dir, and--update parameters. The following command block uses an example symlink of/usr/local/bin and example installer location of/usr/local/aws-cli.

$curl "https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip" -o "awscliv2.zip"unzip awscliv2.zipsudo ./aws/install --bin-dir/usr/local/bin --install-dir/usr/local/aws-cli --update

Guided installation steps

1. Download the installation file in one of the following ways:

   • Use thecurl command – The-o option specifies the file name that the downloaded package is written to. The options on the following example command write the downloaded file to the current directory with the local nameawscliv2.zip.

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

   • Downloading from the URL – To download the installer with your browser, use the following URL:https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip

2. (Optional) Verifying the integrity of your downloaded zip file

   If you chose to manually download the AWS CLI installer package.zip in the above steps, you can use the following steps to verify the signatures by using theGnuPG tool.

   The AWS CLI installer package.zip files are cryptographically signed using PGP signatures. If there is any damage or alteration of the files, this verification fails and you should not proceed with installation.

   1. Download and install thegpg command using your package manager. For more information aboutGnuPG, see theGnuPG website.

   2. To create the public key file, create a text file and paste in the following text.

      -----BEGIN PGP PUBLIC KEY BLOCK-----mQINBF2Cr7UBEADJZHcgusOJl7ENSyumXh85z0TRV0xJorM2B/JL0kHOyigQluUGZMLhENaG0bYatdrKP+3H91lvK050pXwnO/R7fB/FSTouki4ciIx5OuLlnJZIxSzxPqGl0mkxImLNbGWoi6Lto0LYxqHN2iQtzlwTVmq9733zd3XfcXrZ3+LblHAgEt5GTfNxEKJ8soPLyWmwDH6HWCnjZ/aIQRBTIQ05uVeEoYxSh6wOai7ss/KveoSNBbYzgbdzoqI2Y8cgH2nbfgp3DSasaLZEdCSsIsK1u05CinE7k2qZ7KgKAUIcT/cR/grkC6VwsnDU0OUCideXcQ8WeHutqvgZH1JgKDbznoIzeQHJD238GEu+eKhRHcz8/jeG94zkcgJOz3KbZGYMiTh277Fvj9zzvZsbMBCedV1BTg3TqgvdX4bdkhf5cH+7NtWOlrFj6UwAsGukBTAOxC0l/dnSmZhJ7Z1KmEWilro/gOrjtOxqRQutlIqG22TaqoPGfYVN+en3Zwbt97kcgZDwqbuykNt64oZWc4XKCa3mprEGC3IbJTBFqglXmZ7l9ywGEEUJYOlb2XrSuPWml39beWdKM8kzr1OjnlOm6+lpTRCBfo0wa9F8YZRhHPAkwKkXXDeOGpWRj4ohOx0d2GWkyV5xyN14p2tQOCdOODmz80yUTgRpPVQUtOEhXQARAQABtCFBV1MgQ0xJIFRlYW0gPGF3cy1jbGlAYW1hem9uLmNvbT6JAlQEEwEIAD4CGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AWIQT7Xbd/1cEYuAURraimMQrMRnJHXAUCaGveYQUJDMpiLAAKCRCmMQrMRnJHXKBYD/9Ab0qQdGiO5hObchG8xh8Rpb4Mjyf60JrVo6m8GNjNj6BHkSc8fuTQJ/FaEhaQxj3pjZ3GXPrXjIIVChmICLlFuRXYzrXcPw0lniybypsZEVai5kO0tCNBCCFuMN9RsmmRG8mf7lC4FSTbUDmxG/QlYK+0IV/luJkzxWa+rySkdpm0JdqumjegNRgObdXHAQDWlubWQHWyZyIQ2B4U7AxqSpcdJp6IS4Zds4wVLd1WE5pquYQ8vS2cNlDm4QNg8wTj58e3lKN47hXHMIb6CHxRnb947oJapg189LLPR5koh+EorNkA1wu5mAJtJvy5YMsppy2y/kIjp3lyY6AmPT1posgGk70ZCmToEZ5rbd7ARExtlh76A0cabMDFlEHDIK8RNUOSRr7L64+KxOUegKBfQHb9dADYqqiKqpCbKgvtWlds909Ms74JBgr2KwZCSY1HaOxnIr4CY43QRqAq5YHOay/mU+6whhmdF18vpyK0vfkvvGresWtSXbag7Hkt3XjaEw76BzxQH21EBDqU8WJVjHgU6ru+DJTs+SxgJbaT3hb/vyjlw0lK+hFfhWKRwgOXH8vqducF95NRSUxtS4fpqxWVaw3QV2OWSjbne99A5EPEySzryFTKbMGwaTlAwMCwYevt4YT6eb7NmFhTx0Fis4TalUs+j+c7Kg92pDx2uQ===OBAt-----END PGP PUBLIC KEY BLOCK-----

      For reference, the following are the details of the public key.

      Key ID:           A6310ACC4672475CType:             RSASize:             4096/4096Created:          2019-09-18Expires:          2026-07-07User ID:          AWS CLI Team <aws-cli@amazon.com>Key fingerprint:  FB5D B77F D5C1 18B8 0511  ADA8 A631 0ACC 4672 475C

   3. Import the AWS CLI public key with the following command, substitutingpublic-key-file-name with the file name of the public key you created.

      $gpg --importpublic-key-file-namegpg: /home/username/.gnupg/trustdb.gpg: trustdb createdgpg: key A6310ACC4672475C: public key "AWS CLI Team <aws-cli@amazon.com>" importedgpg: Total number processed: 1gpg:               imported: 1

   4. Download the AWS CLI signature file for the package you downloaded. It has the same path and name as the.zip file it corresponds to, but has the extension.sig. In the following examples, we save it to the current directory as a file namedawscliv2.sig.

      For the latest version of the AWS CLI,use the following command block:

      $curl -o awscliv2.sighttps://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip.sig

   5. Verify the signature, passing both the downloaded.sig and.zip file names as parameters to thegpg command.

      $gpg --verify awscliv2.sig awscliv2.zip

      The output should look similar to the following.

      gpg: Signature made Mon Nov  4 19:00:01 2019 PSTgpg:                using RSA key FB5D B77F D5C1 18B8 0511 ADA8 A631 0ACC 4672 475Cgpg: Good signature from "AWS CLI Team <aws-cli@amazon.com>" [unknown]gpg: WARNING: This key is not certified with a trusted signature!gpg:          There is no indication that the signature belongs to the owner.Primary key fingerprint: FB5D B77F D5C1 18B8 0511  ADA8 A631 0ACC 4672 475C

      Important

      The warning in the output is expected and doesn't indicate a problem. It occurs because there isn't a chain of trust between your personal PGP key (if you have one) and the AWS CLI PGP key. For more information, seeWeb of trust.

3. Unzip the installer. If your Linux distribution doesn't have a built-inunzip command, use an equivalent to unzip it. The following example command unzips the package and creates a directory namedaws under the current directory.

   $unzip awscliv2.zip

   Note

   When updating from a previous version, theunzip command prompts to overwrite existing files. To skip these prompts, such as with script automation, use the-u update flag forunzip. This flag automatically updates existing files and creates new ones as needed.

   $unzip -u awscliv2.zip

4. Run the install program. The installation command uses a file namedinstall in the newly unzippedaws directory. By default, the files are all installed to/usr/local/aws-cli, and a symbolic link is created in/usr/local/bin. The command includessudo to grant write permissions to those directories.

   $sudo ./aws/install

   You can install withoutsudo if you specify directories that you already have write permissions to. Use the following instructions for theinstall command to specify the installation location:

   • Ensure that the paths you provide to the-i and-b parameters contain no volume name or directory names that contain any space characters or other white space characters. If there is a space, the installation fails.

   • --install-dir or-i – This option specifies the directory to copy all of the files to.

     The default value is/usr/local/aws-cli.

   • --bin-dir or-b – This option specifies that the mainaws program in the install directory is symbolically linked to the fileaws in the specified path. You must have write permissions to the specified directory. Creating a symlink to a directory that is already in your path eliminates the need to add the install directory to the user's$PATH variable.

     The default value is/usr/local/bin.

   $./aws/install -i/usr/local/aws-cli -b/usr/local/bin

   Note

   To update your current installation of the AWS CLI, add your existing symlink and installer information to construct theinstall command with the--update parameter.

   $sudo ./aws/install --bin-dir/usr/local/bin --install-dir/usr/local/aws-cli --update

   To locate the existing symlink and installation directory, use the following steps:

   1. Use thewhich command to find your symlink. This gives you the path to use with the--bin-dir parameter.

      $which aws/usr/local/bin/aws

   2. Use thels command to find the directory that your symlink points to. This gives you the path to use with the--install-dir parameter.

      $ls -l /usr/local/bin/awslrwxrwxrwx 1 ec2-user ec2-user 49 Oct 22 09:49 /usr/local/bin/aws ->/usr/local/aws-cli/v2/current/bin/aws

5. Confirm the installation with the following command.

   $aws --versionaws-cli/2.27.41 Python/3.11.6 Linux/5.10.205-195.807.amzn2.x86_64

   If theaws command cannot be found, you might need to restart your terminal or follow the troubleshooting inTroubleshooting errors for the AWS CLI.

Snap package

We provide an official AWS supported version of the AWS CLI onsnap. If you want to always have the latest version of the AWS CLI installed on your system, a snap package provides this for you as it auto-updates. There is no built-in support for selecting minor versions of AWS CLI and therefore it is not an optimal install method if your team needs to pin versions. If you want to install a specific minor version of the AWS CLI, we suggest you use the command line installer.

1. If your Linux platform does not already havesnap installed, installsnap on your platform.

   1. For information on installingsnap, seeInstalling the daemon in theSnap documentation.

   2. You may need to restart your system so that yourPATH variables are updated correctly. If you are having installation issues, follow steps inFix common issues in theSnap documentation.

   3. To verify thatsnap is installed correctly, run the following command.

      $snap version

2. Run the followingsnap install command for the AWS CLI.

   $snap install aws-cli --classic

   Depending on your permissions, you may need to addsudo to the command.

   $sudo snap install aws-cli --classic

   Note

   To view the snap repository for the AWS CLI, including additionalsnap instructions, see theaws-cli page in theCanonical Snapcraft website.

3. Verify that the AWS CLI installed correctly.

   $aws --versionaws-cli/2.27.41 Python/3.11.6 Linux/5.10.205-195.807.amzn2.x86_64

   If you get an error, seeTroubleshooting errors for the AWS CLI.

macOS version support matrix

Install or update the AWS CLI

If you are updating to the latest version, use the same installation method that you used in your current version. You can install the AWS CLI on macOS in the following ways.

GUI installer

The following steps show how to install the latest version of the AWS CLI by using the standard macOS user interface and your browser.

1. In your browser, download the macOSpkg file:https://awscli.amazonaws.com/AWSCLIV2.pkg

2. Run your downloaded file and follow the on-screen instructions. You can choose to install the AWS CLI in the following ways:

   • For all users on the computer (requiressudo)

     • You can install to any folder, or choose the recommended default folder of/usr/local/aws-cli.

     • The installer automatically creates a symlink at/usr/local/bin/aws that links to the main program in the installation folder you chose.

   • For only the current user (doesn't requiresudo)

     • You can install to any folder to which you have write permission.

     • Due to standard user permissions, after the installer finishes, you must manually create a symlink file in your$PATH that points to theaws andaws_completer programs by using the following commands at the command prompt. The default location for a symlink is/usr/local/bin/:

       $ln -s /folder/installed/aws-cli/aws /usr/local/bin/aws$ln -s /folder/installed/aws-cli/aws_completer /usr/local/bin/aws_completer

       If you don't have write permissions to the folder, you may need to usesudo in your command. The following example usessudo with the default location for a symlink in/usr/local/bin/:

       $sudo ln -s /folder/installed/aws-cli/aws /usr/local/bin/aws$sudo ln -s /folder/installed/aws-cli/aws_completer /usr/local/bin/aws_completer

   Note

   You can view debug logs for the installation by pressingCmd+L anywhere in the installer. This opens a log pane that enables you to filter and save the log. The log file is also automatically saved to/var/log/install.log.

3. To verify that the shell can find and run theaws command in your$PATH, use the following commands.

   $which aws/usr/local/bin/aws$aws --versionaws-cli/2.27.41 Python/3.11.6 Darwin/23.3.0

   If theaws command cannot be found, you might need to restart your terminal or follow the troubleshooting inTroubleshooting errors for the AWS CLI.

Command line installer - All users

If you havesudo permissions, you can install the AWS CLI for all users on the computer. We provide the steps in one easy to copy and paste group. See the descriptions of each line in the following steps.

$curl "https://awscli.amazonaws.com/AWSCLIV2.pkg" -o "AWSCLIV2.pkg"$sudo installer -pkg AWSCLIV2.pkg -target /

Guided installation instructions

1. Download the file using thecurl command. The-o option specifies the file name that the downloaded package is written to. In this example, the file is written toAWSCLIV2.pkg in the current folder.

   $curl "https://awscli.amazonaws.com/AWSCLIV2.pkg" -o "AWSCLIV2.pkg"

2. Run the standard macOSinstaller program, specifying the downloaded.pkg file as the source. Use the-pkg parameter to specify the name of the package to install, and the-target / parameter for which drive to install the package to. The files are installed to/usr/local/aws-cli, and a symlink is automatically created in/usr/local/bin. You must includesudo on the command to grant write permissions to those folders.

   $sudo installer -pkg ./AWSCLIV2.pkg -target /

   After installation is complete, debug logs are written to/var/log/install.log.

3. To verify that the shell can find and run theaws command in your$PATH, use the following commands.

   $which aws/usr/local/bin/aws$aws --versionaws-cli/2.27.41 Python/3.11.6 Darwin/23.3.0

   If theaws command cannot be found, you might need to restart your terminal or follow the troubleshooting inTroubleshooting errors for the AWS CLI.

Command line - Current user

1. To specify which folder the AWS CLI is installed to, you must create an XML file with any file name. This file is an XML-formatted file that looks like the following example. Leave all values as shown, except you must replace the path/Users/myusername in line 9 with the path to the folder you want the AWS CLI installed to.The folder must already exist, or the command fails. The following XML example, namedchoices.xml, specifies the installer to install the AWS CLI in the folder/Users/myusername, where it creates a folder namedaws-cli.

   <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><plist version="1.0">  <array>    <dict>      <key>choiceAttribute</key>      <string>customLocation</string>      <key>attributeSetting</key>      <string>/Users/myusername</string>      <key>choiceIdentifier</key>      <string>default</string>    </dict>  </array></plist>

2. Download thepkg installer using thecurl command. The-o option specifies the file name that the downloaded package is written to. In this example, the file is written toAWSCLIV2.pkg in the current folder.

   $curl "https://awscli.amazonaws.com/AWSCLIV2.pkg" -o "AWSCLIV2.pkg"

3. Run the standard macOSinstaller program with the following options:

   • Specify the name of the package to install by using the-pkg parameter.

   • Specify installing to acurrent user only by setting the-target parameter toCurrentUserHomeDirectory.

   • Specify the path (relative to the current folder) and name of the XML file that you created in the-applyChoiceChangesXML parameter.

   The following example installs the AWS CLI in the folder/Users/myusername/aws-cli.

   $installer -pkg AWSCLIV2.pkg \            -target CurrentUserHomeDirectory \            -applyChoiceChangesXMLchoices.xml

4. Because standard user permissions typically don't allow writing to folders in your$PATH, the installer in this mode doesn't try to add the symlinks to theaws andaws_completer programs. For the AWS CLI to run correctly, you must manually create the symlinks after the installer finishes. If your$PATH includes a folder you can write to and you specify the folder as the target's path, you can run the following command withoutsudo. If you don't have a writable folder in your$PATH, you must usesudo for permissions to write to the specified target folder. The default location for a symlink is/usr/local/bin/. Replacefolder/installed with the path to your AWS CLI installation.

   $sudo ln -s /folder/installed/aws-cli/aws /usr/local/bin/aws$sudo ln -s /folder/installed/aws-cli/aws_completer /usr/local/bin/aws_completer

   After installation is complete, debug logs are written to/var/log/install.log.

5. To verify that the shell can find and run theaws command in your$PATH, use the following commands.

   $which aws/usr/local/bin/aws$aws --versionaws-cli/2.27.41 Python/3.11.6 Darwin/23.3.0

   If theaws command cannot be found, you might need to restart your terminal or follow the troubleshooting inTroubleshooting errors for the AWS CLI.

To update your current installation of AWS CLI on Windows, download a new installer each time you update to overwrite previous versions. AWS CLI is updated regularly. To see when the latest version was released, see theAWS CLI version 2 Changelog onGitHub.