|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Aws Cli||14,298||2,710||337||2 days ago||1,766||August 02, 2023||525||other||Python|
|Universal Command Line Interface for Amazon Web Services|
|Aws Vault||7,717||1||5||a month ago||103||March 20, 2023||50||mit||Go|
|A vault for securely storing and accessing AWS credentials in development environments|
|Terragrunt||7,174||16||19 hours ago||480||August 02, 2023||592||mit||Go|
|Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.|
|Aws Shell||6,915||23||3||4 months ago||6||October 07, 2020||98||apache-2.0||Python|
|An integrated shell for working with the AWS CLI.|
|Aws Sam Cli||6,374||31||12||19 hours ago||168||July 27, 2023||387||apache-2.0||Python|
|CLI tool to build, test, debug, and deploy Serverless applications using AWS SAM|
|Dev Setup||5,802||a year ago||34||other||Python|
|Saws||4,906||8||2 years ago||9||April 09, 2017||35||other||Python|
|A supercharged AWS command line interface (CLI).|
|Awless||4,827||1||2 years ago||20||December 10, 2018||124||apache-2.0||Go|
|A Mighty CLI for AWS|
|Aws Nuke||4,784||2||2||a day ago||60||June 20, 2023||201||mit||Go|
|Nuke a whole AWS account and delete all its resources.|
|Copilot Cli||3,069||21 hours ago||54||August 01, 2023||537||apache-2.0||Go|
|The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.|
This package provides a unified command line interface to Amazon Web Services.
This README is for the AWS CLI version 1. If you are looking for information about the AWS CLI version 2, please visit the v2 branch.
The aws-cli package works on Python versions:
On 2021-01-15, deprecation for Python 2.7 was announced and support was dropped on 2021-07-15. To avoid disruption, customers using the AWS CLI on Python 2.7 may need to upgrade their version of Python or pin the version of the AWS CLI. For more information, see this blog post.
We recommend that all customers regularly monitor the Amazon Web Services Security Bulletins website for any important security bulletins related to aws-cli.
The AWS CLI version 1 was made generally available on 09/02/2013 and is currently in the full support phase of the availability life cycle.
For information about maintenance and support for SDK major versions and their underlying dependencies, see the Maintenance Policy section in the AWS SDKs and Tools Shared Configuration and Credentials Reference Guide.
Installation of the AWS CLI and its dependencies use a range of packaging
features provided by
setuptools. To ensure smooth installation,
it's recommended to use:
pip: 9.0.2 or greater
setuptools: 36.2.0 or greater
The safest way to install the AWS CLI is to use
pip in a
$ python -m pip install awscli
or, if you are not installing in a
virtualenv, to install globally:
$ sudo python -m pip install awscli
or for your user:
$ python -m pip install --user awscli
If you have the aws-cli package installed and want to upgrade to the latest version, you can run:
$ python -m pip install --upgrade awscli
This will install the aws-cli package as well as all dependencies.
On macOS, if you see an error regarding the version of
distutils in El Capitan, use the
$ sudo python -m pip install awscli --ignore-installed six
If you want to run the
develop branch of the AWS CLI, see the
Development Version section of
the contributing guide.
See the installation section of the AWS CLI User Guide for more information.
Before using the AWS CLI, you need to configure your AWS credentials. You can do this in several ways:
The quickest way to get started is to run the
aws configure command:
$ aws configure AWS Access Key ID: MYACCESSKEY AWS Secret Access Key: MYSECRETKEY Default region name [us-west-2]: us-west-2 Default output format [None]: json
To use environment variables, do the following:
$ export AWS_ACCESS_KEY_ID=<access_key> $ export AWS_SECRET_ACCESS_KEY=<secret_key>
To use the shared credentials file, create an INI formatted file like this:
[default] aws_access_key_id=MYACCESSKEY aws_secret_access_key=MYSECRETKEY [testing] aws_access_key_id=MYACCESKEY aws_secret_access_key=MYSECRETKEY
and place it in
~/.aws/credentials (or in
%UserProfile%\.aws/credentials on Windows). If you wish to place the
shared credentials file in a different location than the one specified
above, you need to tell aws-cli where to find it. Do this by setting the
appropriate environment variable:
$ export AWS_SHARED_CREDENTIALS_FILE=/path/to/shared_credentials_file
To use a config file, create an INI formatted file like this:
[default] aws_access_key_id=<default access key> aws_secret_access_key=<default secret key> # Optional, to define default region for this profile. region=us-west-1 [profile testing] aws_access_key_id=<testing access key> aws_secret_access_key=<testing secret key> region=us-west-2
and place it in
~/.aws/config (or in
on Windows). If you wish to place the config file in a different
location than the one specified above, you need to tell the AWS CLI
where to find it. Do this by setting the appropriate environment
$ export AWS_CONFIG_FILE=/path/to/config_file
As you can see, you can have multiple
profiles defined in both the
shared credentials file and the configuration file. You can then specify
which profile to use by using the
--profile option. If no profile is
default profile is used.
In the config file, except for the default profile, you must prefix
each config section of a profile group with
profile. For example, if
you have a profile named "testing" the section header would be
The final option for credentials is highly recommended if you are using the AWS CLI on an EC2 instance. IAM Roles are a great way to have credentials installed automatically on your instance. If you are using IAM Roles, the AWS CLI will find and use them automatically.
In addition to credentials, a number of other variables can be configured either with environment variables, configuration file entries, or both. See the AWS Tools and SDKs Shared Configuration and Credentials Reference Guide for more information.
For more information about configuration options, please refer to the
AWS CLI Configuration Variables
You can access this topic from the AWS CLI as well by running
aws help config-vars.
An AWS CLI command has the following structure:
$ aws <command> <subcommand> [options and parameters]
For example, to list S3 buckets, the command would be:
$ aws s3 ls
To view help documentation, use one of the following:
$ aws help $ aws <command> help $ aws <command> <subcommand> help
To get the version of the AWS CLI:
$ aws --version
To turn on debugging output:
$ aws --debug <command> <subcommand>
You can read more information on the Using the AWS CLI chapter of the AWS CLI User Guide.
The aws-cli package includes a command completion feature for Unix-like systems. This feature is not automatically installed so you need to configure it manually. To learn more, read the AWS CLI Command completion topic.
The best way to interact with our team is through GitHub. You can open an issue and choose from one of our templates for guidance, bug reports, or feature requests.
You may find help from the community on Stack Overflow with the tag aws-cli or on the AWS Discussion Forum for CLI. If you have a support plan with AWS Support, you can also create a new support case.
Please check for open similar issues before opening another one.
The AWS CLI implements AWS service APIs. For general issues regarding the services or their limitations, you may find the Amazon Web Services Discussion Forums helpful.