This article is a technical explanation and implementation example created using AI. The published code and procedures are based on primary sources, but operation checks on actual equipment have not been performed by the author. Operations may vary depending on the environment and version.
Checking AWS CLI Configuration Precedence and Read Operations from Official Information
The AWS Command Line Interface (AWS CLI) is an open-source tool for managing AWS services from your command-line shell. It is designed to allow you to perform functionality equivalent to the browser-based AWS Management Console from your command prompt or terminal. This article organizes the basic concepts of the AWS CLI, the features of version 2, the usage environment, and the concepts of configuration and operations that can be read from official information, based on the official user guide (version 2).
[Before Actual Equipment Verification] The contents handled in this article are based on descriptions in primary sources, and specific execution results or operations have not been measured or verified in the author’s environment.
AWS CLI Overview and Usage Environment
By using the AWS CLI, developers can directly access AWS public APIs through a terminal or shell program. All infrastructure management, access, and administration features provided in the Management Console are available through the AWS API and the AWS CLI. New features and new services are also provided with full functionality via the CLI and API at launch or within 180 days of launch.
The official guide explains that commands can be executed in various environments such as the following:
Linux Shell: Execute commands using common shell programs such as
bash,zsh, andtcshon Linux or macOS.Windows Command Line: Execute commands in the Windows Command Prompt or PowerShell.
Remote Environment: Execute commands on Amazon EC2 instances via remote terminal programs using PuTTY or SSH, or via AWS Systems Manager.
In addition, as basic AWS knowledge, it is mentioned that digital infrastructure services such as computing, storage, databases, and application synchronization (messaging and queuing) are provided on a pay-as-you-go model. To make it easier to prototype and experiment with the platform, a Free Tier is also available, which is free up to a certain usage limit.
Processing Flow Using AWS CLI
In operations using the AWS CLI, requests are sent from the local terminal to AWS services via various shells or remote environments. The following Mermaid diagram organizes the usage environment and the basic positioning of the CLI described in the primary source.
flowchart TD
Terminal["Terminal / Shell Environment<br>Linux / macOS / Windows / Remote"] --> CLI["AWS CLI Version 2"]
CLI --> API["AWS Public APIs"]
API --> Services["AWS Services<br>Computing / Storage / Database etc."]
As shown in this diagram, users invoke the AWS CLI from their familiar shell program, which interacts with each AWS service through the underlying public API.
Features and Management Policy of AWS CLI Version 2
Version 2, the latest major version of the AWS CLI, supports all the latest features. Because some features introduced in version 2 are not backported to version 1, upgrading to version 2 is required to use the latest features. In addition, “breaking” changes from version 1 may be included, requiring modification of existing scripts. Detailed changes are described in the version 2 migration guide.
Official guidance is also provided regarding installation methods. AWS CLI version 2 can only be installed using the bundled installer. While there are cases where it is provided via package managers, these are unofficial and unsupported packages that are not produced or managed by AWS. Therefore, it is recommended to install only from the official distribution points documented in the official guide.
Official information states that the following command should be used to check the currently installed version:
aws --version
It is guided that executing the version check command outputs version information, Python version, OS information, and botocore version in a format like the following.
aws-cli/2.27.41 Python/3.11.6 Linux/5.10.205-195.807.amzn2.x86_64 botocore/1.18.6
[Before Actual Equipment Verification] The output example above is an illustration described in the primary source and is not a measured value in the author’s environment at the time of writing.
Version History and SDK Support Policy
For the version history of AWS CLI version 2, it is guided to refer to the AWS CLI version 2 Changelog on GitHub.
Furthermore, information regarding the maintenance and support of major versions of SDKs and their underlying dependencies is summarized in detail in the AWS SDKs and Tools Reference Guide. Specifically, the following documents are cited as reference destinations:
AWS SDKs and tools maintenance policy
AWS SDKs and tools version support matrix
By referring to these, you can understand the support lifecycle of the tools and SDKs you use and create a stable operation plan.
Low-Level Commands and Custom Commands
The AWS CLI provides low-level commands that correspond one-to-one with APIs. This allows you to thoroughly explore service features and create shell scripts to manage resources with fine granularity.
On the other hand, in addition to low-level commands, customization features for the AWS CLI are provided by some AWS services. These customizations may include high-level commands to simplify the use of services with complex APIs. This is designed to allow users to manipulate resources more intuitively and efficiently.
Precautions and Summary
When using the AWS CLI, it is important to choose the correct installation method according to the official documentation and to pay attention to the changes when migrating from version 1 to version 2. Since unofficial installation methods using package managers are considered unsupported, be sure to check the instructions on the official website. Based on the official user guide, this article has organized the basic positioning of the AWS CLI, features of version 2, usage environment, and the mechanism of version checking and customization features. For detailed command references and specific migration procedures, please refer to the following reference information.
コメント