Installing AWS CLI - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding AWS CLI Installation Methods

Which of the following is the recommended method to install the AWS CLI on a Windows machine to ensure automatic updates?

A Download and run the MSI installer from the official AWS website.

B Use the Windows Store to install the AWS CLI application.

C Install AWS CLI using pip with the command <code>pip install awscli</code>.

D Manually download the AWS CLI zip file and extract it to a folder.

💡 Hint

Consider which method is officially supported and provides easy updates.

The MSI installer from AWS is the official recommended method for Windows. It sets up the CLI properly and supports automatic updates. Using pip is possible but not recommended on Windows for AWS CLI v2. The Windows Store does not offer AWS CLI. Manual extraction lacks update support.

❓ Configuration

intermediate

Verifying AWS CLI Installation on Linux

After installing AWS CLI version 2 on a Linux system, which command correctly verifies the installed version?

A aws -v

B aws version

C awscli --check-version

D aws --version

💡 Hint

Think about the standard way most command-line tools show their version.

The correct command to check AWS CLI version is aws --version. Other options are invalid or produce errors.

❓ Architecture

advanced

Choosing AWS CLI Version for Automation Scripts

You need to write automation scripts that interact with AWS services on a macOS system. Which AWS CLI version should you install to ensure compatibility with the latest AWS features and long-term support?

A AWS CLI version 1 installed via pip.

B AWS CLI version 2 installed using the official bundled installer.

C AWS CLI version 1 installed using the macOS package manager Homebrew.

D AWS CLI version 2 installed manually by downloading the source code and compiling.

💡 Hint

Consider which version is actively maintained and officially recommended for new features.

AWS CLI version 2 is the current major version with new features and support. Installing it via the official bundled installer on macOS ensures compatibility and updates. Version 1 is deprecated. Manual compilation is not supported for AWS CLI v2.

❓ security

advanced

Securing AWS CLI Credentials After Installation

After installing AWS CLI on a Linux server, what is the best practice to securely store AWS credentials for automated scripts?

A Store AWS access keys in the <code>~/.aws/credentials</code> file with strict file permissions.

B Use the AWS CLI without credentials and rely on anonymous access.

C Set AWS access keys as environment variables globally for all users.

D Embed AWS access keys directly inside the automation script source code.

💡 Hint

Think about protecting sensitive information and limiting access.

The recommended practice is to store credentials in the ~/.aws/credentials file with permissions set to allow only the user to read it. Embedding keys in scripts or environment variables globally risks exposure. Anonymous access is not practical for most AWS operations.

❓ service_behavior

expert

Effect of AWS CLI Version on Service Command Availability

You installed AWS CLI version 1 on a Windows machine. You try to run a command for a new AWS service released recently, but it fails with 'Unknown command'. What is the most likely reason?

A The AWS service is not available in the region configured in AWS CLI.

B The AWS CLI installation is corrupted and needs to be reinstalled.

C AWS CLI version 1 does not include commands for newly released AWS services; upgrading to version 2 is required.

D The command syntax is incorrect and needs to be checked.

💡 Hint

Consider the relationship between AWS CLI versions and service support.

AWS CLI version 1 is no longer updated with new service commands. New AWS services require AWS CLI version 2 or later. While region and syntax issues can cause errors, the specific 'Unknown command' error for a new service usually means the CLI version is outdated.

Practice

1. What is the primary purpose of installing the AWS CLI on your computer?

easy

A. To control AWS services using command-line commands

B. To create graphical dashboards for AWS

C. To run AWS services locally without internet

D. To automatically update AWS services

Solution

1. Step 1: Understand AWS CLI functionality

   AWS CLI allows users to interact with AWS services using commands typed in a terminal or command prompt.

2. Step 2: Identify the main use case

   The main use is to control and manage AWS resources from your computer without using the web console.

3. Final Answer:

   To control AWS services using command-line commands -> Option A

4. Quick Check:

   AWS CLI = command-line control [OK]

Hint: AWS CLI means command-line tool for AWS control [OK]

Common Mistakes:

• Thinking AWS CLI creates graphical interfaces
• Believing AWS CLI runs AWS services offline
• Assuming AWS CLI updates AWS automatically

2. Which command correctly checks if AWS CLI is installed and shows its version?

easy

A. aws version check

B. aws --version

C. check aws version

D. aws -v check

Solution

1. Step 1: Recall the AWS CLI version command

   The official command to check AWS CLI version is aws --version.

2. Step 2: Compare options

   Only aws --version matches the correct syntax; others are invalid commands.

3. Final Answer:

   aws --version -> Option B

4. Quick Check:

   Check version = aws --version [OK]

Hint: Use double dash before version to check AWS CLI [OK]

Common Mistakes:

• Using single dash instead of double dash
• Reversing command order
• Adding extra words like 'check'

3. After installing AWS CLI, you run aws configure. What information does this command ask you to enter?

medium

A. AWS username and password

B. AWS service names to enable

C. AWS billing details

D. AWS Access Key ID, Secret Access Key, region, and output format

Solution

1. Step 1: Understand purpose of aws configure

   This command sets up credentials and default settings for AWS CLI to work.

2. Step 2: Identify required inputs

   It asks for Access Key ID, Secret Access Key, default region, and output format (like json).

3. Final Answer:

   AWS Access Key ID, Secret Access Key, region, and output format -> Option D

4. Quick Check:

   Configure = keys + region + output [OK]

Hint: Configure sets keys, region, and output format [OK]

Common Mistakes:

• Entering username/password instead of keys
• Confusing billing info with credentials
• Trying to enable services here

4. You installed AWS CLI but running aws --version gives an error 'command not found'. What is the likely cause?

medium

A. AWS CLI is not added to your system PATH environment variable

B. You typed the command incorrectly

C. Your internet connection is down

D. AWS CLI requires a password to run

Solution

1. Step 1: Understand 'command not found' error

   This error means the system cannot find the program to run it.

2. Step 2: Identify common cause

   Usually, the AWS CLI executable is not in the system PATH, so the terminal can't locate it.

3. Final Answer:

   AWS CLI is not added to your system PATH environment variable -> Option A

4. Quick Check:

   Command not found = PATH missing [OK]

Hint: Add AWS CLI to PATH to fix 'command not found' error [OK]

Common Mistakes:

• Assuming internet is needed to run version command
• Thinking password is required to run CLI
• Ignoring PATH environment variable

5. You want to install AWS CLI on a Windows computer. Which of the following steps correctly describes the process?

hard

A. Download the Linux package and run it using Windows Subsystem for Linux

B. Open PowerShell and type install aws-cli to install automatically

C. Download the Windows MSI installer from AWS website, run it, then open Command Prompt and run aws --version

D. Use the AWS web console to install AWS CLI remotely

Solution

1. Step 1: Identify correct installation method for Windows

   For Windows, AWS provides an MSI installer downloadable from their website.

2. Step 2: Verify installation

   After running the installer, open Command Prompt and run aws --version to confirm installation.

3. Final Answer:

   Download the Windows MSI installer from AWS website, run it, then open Command Prompt and run aws --version -> Option C

4. Quick Check:

   Windows install = MSI + verify version [OK]

Hint: Use MSI installer on Windows, then check version [OK]

Common Mistakes:

• Trying Linux package directly on Windows
• Assuming PowerShell has install command
• Thinking AWS web console installs CLI