How To Start Aws Cli On Windows

How To Install And Configure AWS CLI On Windows OS

Hi Anybody

Welcome to CloudAffaire and this is Debjeet.

In this blog mail service, we will discuss how to install and configure AWS CLI on Windows Os. AWS Command Line Interface (AWS CLI) is an open-source tool that enables you to interact with AWS services using commands in your command-line trounce. With minimal configuration, you can offset using functionality equivalent to AWS Direction Console from the command prompt in your favorite terminal programme. AWS CLI supports all the major operating systems and using AWS CLI you lot tin administer all the IaaS (infrastructure as a service) services provided by AWS.

Prerequisites:

• Ane agile AWS account with admin access.
• Windows XP or later Os version with admin access.

How To Install AWS CLI On Windows OS:

Step 1: Log in to your windows arrangement and download the latest version of AWS CLI using the below link.

https://awscli.amazonaws.com/AWSCLIV2.msi

Step ii: Double click on the downloaded installer and click on "Run".

Step 3: Follow the installation wizard and click 'Install' to install AWS CLI on your system.

Click on 'Stop' once the installation is completed.

Step 4: Validate the installation past executing the below command on the control prompt.

If y'all become the AWS CLI version that means your installation was successful. Next, we are going to configure AWS CLI.

How to configure AWS CLI on Windows OS:

AWS CLI require three mandatory parameters (access_key, secret_key,and region) to access the resource in your AWS business relationship. You get the access_key and secret_key, when you lot create an IAM user with programmatic access or assume a role. The region parameter defines the region where AWS CLI volition interact with the resources.

AWS CLI Configuration Parameters:

There are several configuration parameters available for AWS CLI that tin be passed forth with AWS CLI commands.

• access_key: Specifies an AWS access key associated with an IAM user or role.
• secret_key: Specifies the surreptitious key associated with the access key. This is essentially the "countersign" for the access key.
• region: Specifies the AWS Region to send the request to.
• output: Specifies the output format to use. Output can be in text, json or table format.
• contour: Specifies the proper noun of the CLI profile with the credentials and options to use. This tin be the proper noun of a contour stored in a credentials or config file
• session_token: Specifies an AWS session token. Used when you assume an IAM role.
• ca_bundle: Specifies a CA certificate package (a file with the .pem extension) that is used to verify SSL certificates.

AWS CLI Configuration Options:

In that location are several ways you can configure AWS CLI. The AWS CLI uses a set up of credential providers to look for AWS credentials. Each credential provider looks for credentials in a dissimilar place, such as the system or user environment variables, local AWS configuration files, or explicitly declared on the command line as a parameter. Beneath is the precedence order for configuration settings.

• Control line options: Value that are passed direct (for example –region) with aws cli has the highest precedence.
• Environment variables: Value that are set as environment variable (for example AWS_DEFAULT_REGION) has the 2nd highest precedence.
• Configuration Files: Values that are divers in configuration files (for instance region in config file) has lowest precedence.

Using Configuration Files: You can save your frequently used configuration settings and credentials in files that are maintained by the AWS CLI. The files are divided into sections that tin be referenced past name. These are called "profiles". Unless you specify otherwise, the CLI uses the settings institute in the contour named default. To utilize alternate settings, you tin create and reference additional profiles.

Using Surroundings Variables: Environs variables provide another way to specify configuration options and credentials, and can be useful for scripting or temporarily setting a named profile equally the default.

Using Case Contour: When you lot run the AWS CLI from within an Amazon EC2 instance, you tin can simplify providing credentials to your commands. Each Amazon EC2 instance contains metadata that the AWS CLI can straight query for temporary credentials. To provide these, create an AWS Identity and Admission Direction (IAM) function that has access to the resources needed, and adhere that function to the AWS EC2 example when y'all launch information technology.

Next, nosotros will configure AWS CLI using the configuration file selection.

Prerequisite for this demo:

• One IAM user having admin access to AWS with programmatic access.

You can refer below blog posts to create IAM users.

https://cloudaffaire.com/iam-users/

Step 1: Open up a control prompt and type 'aws configure'. Provide the IAM user 'Access Key' and 'Undercover Key' and the default region for your AWS infra.

Step 2: Validate the AWS CLI configuration using the beneath control.

aws sts get - caller - identity

Note: In Windows, the configuration files will be created in C:\Users\<USERNAME>\.aws\config location and In Linux, the config files volition exist created in ~/.aws/ location.

Step iii: Execute your 1^st AWS CLI command.

aws ec2 draw - vpcs -- output text -- query "Vpcs[*].[VpcId]"

Hope you lot accept enjoyed this blog post. To install AWS CLI on a dissimilar Os, please refer below AWS documentation.

https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html

Source: https://cloudaffaire.com/how-to-install-and-configure-aws-cli-on-windows-os/

Posted by: olivasbobsoo.blogspot.com

Share this post