How To Install Aws Cli On Linux – Configuring Access Key Credentials

by

AWS CLI on Linux enables command-line control over cloud resources for automated infrastructure management. If you are wondering How To Install Aws Cli On Linux, you have come to the right place. This guide will walk you through every step, from prerequisites to verification, ensuring you can start managing your AWS services directly from your terminal.

Whether you are a system administrator, a DevOps engineer, or a developer, installing the AWS CLI is a fundamental skill. It allows you to script deployments, manage S3 buckets, launch EC2 instances, and much more without touching the AWS Management Console. Let’s get started with the simplest methods first.

Prerequisites For Installation

Before you begin, make sure your Linux system meets the basic requirements. You need a working internet connection and sudo or root access to install packages. Most modern Linux distributions like Ubuntu, Debian, CentOS, RHEL, Fedora, or Amazon Linux will work fine.

  • A Linux distribution with a package manager (apt, yum, dnf, or zypper).
  • Python 3.6 or later installed (check with python3 --version).
  • Access to a terminal emulator.
  • An AWS account with IAM credentials (Access Key ID and Secret Access Key).

If you don’t have Python 3, you can install it easily. For Ubuntu/Debian, use sudo apt update && sudo apt install python3 python3-pip -y. For CentOS/RHEL, use sudo yum install python3 python3-pip -y. Now you are ready to proceed.

How To Install Aws Cli On Linux

There are multiple ways to install the AWS CLI on Linux. The recommended method is using the official bundled installer, but you can also use pip or package managers. We will cover all three approaches so you can choose the one that fits your workflow best.

Method 1: Using The Official Bundled Installer

This is the most straightforward method. The bundled installer includes all dependencies, so you don’t need to worry about Python versions or pip conflicts. Follow these steps:

  1. Open your terminal.
  2. Download the installer using curl: curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
  3. Unzip the file: unzip awscliv2.zip
  4. Run the install script: sudo ./aws/install
  5. Verify the installation: aws --version

That’s it! The installer places the AWS CLI binary in /usr/local/bin/aws. You can now use it immediately. If you get a permission error, ensure you used sudo. The unzip command may require you to install unzip first: sudo apt install unzip or sudo yum install unzip.

Method 2: Installing With Pip

If you prefer using Python’s package manager, pip is a great alternative. This method works well if you already have Python and pip configured. However, you must ensure you are using a virtual environment to avoid conflicts with system packages.

  1. Update pip: python3 -m pip install --upgrade pip
  2. Install the AWS CLI: python3 -m pip install awscli
  3. Verify the installation: aws --version

If you encounter permission issues, consider using the --user flag: python3 -m pip install --user awscli. This installs the CLI in your home directory. You may need to add ~/.local/bin to your PATH if it isn’t already.

Method 3: Using Package Managers (Apt, Yum, Dnf)

Some Linux distributions offer the AWS CLI through their official repositories. This method is convenient but may provide an older version. Use it only if you don’t need the latest features.

For Ubuntu/Debian:

  • sudo apt update
  • sudo apt install awscli

For CentOS/RHEL/Fedora:

  • sudo yum install awscli (or sudo dnf install awscli on Fedora)

After installation, check the version with aws --version. If it’s outdated, consider using the bundled installer instead.

Configuring The AWS CLI

Once the CLI is installed, you need to configure it with your credentials. Run the configuration command:

aws configure

You will be prompted for:

  • AWS Access Key ID
  • AWS Secret Access Key
  • Default region (e.g., us-east-1)
  • Default output format (json, text, or table)

Your credentials are stored in ~/.aws/credentials, and the config is in ~/.aws/config. You can also set environment variables like AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY for temporary sessions.

Using Multiple Profiles

If you manage multiple AWS accounts, you can create named profiles. Use aws configure --profile prod to set up a profile called “prod”. Then specify it with commands: aws s3 ls --profile prod. This is very useful for separating work and personal accounts.

Verifying The Installation

To confirm everything is working, run a simple command like listing S3 buckets:

aws s3 ls

If you don’t have any buckets, it will return nothing (no error). You can also check your identity:

aws sts get-caller-identity

This should return your account ID, user ID, and ARN. If you see an error, double-check your credentials and region settings.

Troubleshooting Common Issues

Even with a straightforward installation, you might run into problems. Here are some frequent issues and their solutions:

  • Command not found: Ensure the installation directory is in your PATH. For bundled installer, it’s usually /usr/local/bin. For pip user install, add export PATH=$PATH:~/.local/bin to your .bashrc.
  • Permission denied: Use sudo for system-wide installations or use the --user flag with pip.
  • Python version error: The AWS CLI requires Python 3.6+. Check with python3 --version. If you have an older version, upgrade Python first.
  • SSL certificate errors: This can happen on older systems. Update your CA certificates: sudo apt install ca-certificates or sudo yum install ca-certificates.
  • Unzip not found: Install unzip using your package manager before extracting the bundled installer.

Updating The AWS CLI

To keep your CLI up-to-date, you can re-run the bundled installer or use pip. For the bundled installer, download the latest version and run the install script again. For pip, use:

python3 -m pip install --upgrade awscli

Check the version after updating to ensure it succeeded. Regular updates are important to access new AWS features and security patches.

Uninstalling The AWS CLI

If you need to remove the CLI, the method depends on how you installed it. For the bundled installer, run:

sudo /usr/local/bin/aws --uninstall

For pip installations, use:

python3 -m pip uninstall awscli

For package manager installations, use sudo apt remove awscli or sudo yum remove awscli. After uninstalling, verify with aws --version to confirm it’s gone.

Best Practices For Using AWS CLI On Linux

To get the most out of the AWS CLI, follow these tips:

  • Use IAM roles instead of long-term credentials when possible, especially on EC2 instances.
  • Enable MFA for sensitive operations.
  • Use aws help or aws command help to explore available commands.
  • Script repetitive tasks with shell scripts or use AWS CloudFormation.
  • Store credentials securely and never commit them to version control.
  • Use the --dry-run flag to test commands without making changes.

Frequently Asked Questions (FAQ)

1. What is the difference between AWS CLI v1 and v2?

AWS CLI v2 includes new features like interactive workflows, improved pagination, and better SSO support. v1 is still supported but v2 is recommended for new installations.

2. Can I install AWS CLI on Linux without internet access?

Yes, you can download the bundled installer on a machine with internet, transfer it via USB or network, and then install it offline. Ensure dependencies like unzip are already present.

3. How do I install AWS CLI on a specific Linux distribution like Amazon Linux 2?

Amazon Linux 2 often comes with AWS CLI pre-installed. If not, use sudo yum install awscli or the bundled installer. The steps are similar to other distributions.

4. Why do I get “ImportError: No module named awscli” after pip install?

This usually happens when you have multiple Python versions. Use python3 -m pip install awscli instead of just pip install awscli. Also, check your PATH and virtual environment.

5. How can I switch between AWS CLI versions?

You can install both v1 and v2 by using different installation paths. Use the full path to the binary (e.g., /usr/local/bin/aws for v2) or create aliases in your shell profile.

Conclusion

Installing the AWS CLI on Linux is a simple process that opens up powerful automation capabilities. Whether you choose the bundled installer, pip, or your package manager, the steps are clear and easy to follow. Remember to configure your credentials and test with a basic command. With the CLI ready, you can now manage your AWS infrastructure efficiently from the command line. Start exploring the vast array of services at your fingertips.

If you encounter any issues, refer back to the troubleshooting section or consult the official AWS documentation. Happy cloud computing!