The AWS Command Line Interface (CLI) is a unified tool to manage your AWS services. With just one tool to download and configure, you can control multiple AWS services from the command line and automate them through scripts. The AWS CLI v2 offers several new features including improved installers, new configuration options such as AWS Single Sign-On (SSO), and various interactive features. Kindly refer to some of these related guides: AWS ec2 and multi-cloud, How to Deploy MVC Application to AWS EC2 Using RDP, How to Deploy Dynamic Website to AWS EC2, How to host Static Website and Versioning on AWS S3, How to deploy an Angular App to AWS S3. Note: The AWS CLI must be configured on your local workstation simply by downloading it from AWS.
There are different ways to install this but my preferred method is by using an installer that can be downloaded from this site.
Use-Case: Install AWS CLI on Windows
Note: You can also have it installed on MacOS and linux. Please See the URL above for the steps.
The installer can be downloaded here for Windows: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html
After installation, Please verify, it has been installed correctly by using the command below.
Follow the next steps below to configure the AWS CLI
$aws configure AWS Access Key ID [None]: Your Access Key ID AWS Secret Access Key [None]: Your Secret Key Default region name [None]: Enter your desired region in this format (us-west-2) Default output format [None]: I usually leave this by default as (json)
When you type this command, the AWS CLI prompts you for four pieces of information and stores them in a profile (a collection of settings) named
default. This profile is then used any time you run an AWS CLI command that doesn’t explicitly specify a profile to use. Kindly refer to this link for more information.
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.