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.