OSS Tanbou

AWS CLI — operate AWS services through one command structure

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
17,267
Primary language
Python
License
Apache-2.0
Repository last updated
Sep 21, 2026

Overview

AWS CLI is Amazon Web Services' official command-line interface. It exposes service operations through the `aws <service> <operation>` structure and supports profiles and configuration files for switching between environments from terminals, scripts, and CI.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Use one command structure across AWS services

Service operations such as S3 commands live under the aws command and include built-in help for service- and operation-specific parameters.

Sources: [2][3]

Switch environments with profiles and configuration files

Credentials, regions, output formats, and other settings can be stored in profiles and selected with --profile.

Sources: [2][3]

Useful for terminal and automation workflows around AWS

It fits administration, diagnostics, shell scripts, and CI/CD jobs that need a consistent CLI over AWS APIs.

Sources: [3]

Use v2 for new deployments

The default AWS CLI v1 branch is in maintenance mode and no longer receives API updates for new services, existing services, or regions. Follow AWS guidance for v2 and plan migration for remaining v1 environments.

Sources: [2][4]

Official sources

  1. [1]aws/aws-cli repository(2026-09-21)
  2. [2]AWS CLI v1 README(2026-09-21)
  3. [3]AWS CLI v2 README(2026-09-21)
  4. [4]Migrating from AWS CLI v1 to v2(2026-09-21)
  5. [5]AWS CLI Apache-2.0 license(2026-09-21)
Supplemental curator note

The repository's default `develop` branch is AWS CLI v1. Version 1 entered maintenance mode on August 5, 2026 and is scheduled for end of support on July 15, 2027; AWS recommends migrating to v2. New deployments should use v2 and align credential handling with the organization's authentication model rather than relying on long-lived static keys.

Try it in 3 steps

  1. 1

    Install AWS CLI v2 from the official path

    Use the AWS-recommended v2 release rather than the default v1 branch and select the installer for your operating system.

    https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html
  2. 2

    Configure credentials and a region

    Set up a profile according to the organization authentication model, preferring alternatives to long-lived access keys when available.

    aws configure
  3. 3

    Verify the active identity

    Use the read-only STS call to inspect Account, UserId, and Arn before moving on to service-specific operations.

    aws sts get-caller-identity
Check the official README

Growth

Growth trends · Last 30 days

17,267 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
4
Open PRs
233

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • aws
  • cloud
  • aws-cli
  • cloud-management
Stars
17,267
Forks
4,650
Watchers
561
Open issues
507
Contributors
335
Primary language
Python
License
Apache-2.0
Repository last updated
Sep 21, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.