⚙️ AWS CLI Installation

AWS CLI Installation: The AWS CLI is to the AWS Console what a Maven command is to clicking through IntelliJ's GUI — both reach the same outcome, but one can run unattended insid

The AWS CLI is to the AWS Console what a Maven command is to clicking through IntelliJ's GUI — both reach the same outcome, but one can run unattended inside a script at 2 AM. Think about it: if the AWS Console were enough, why does every CI/CD pipeline use the CLI instead? Because a pipeline is just a script, and scripts need commands that return an exit code, pipe their output, and never wait for a human to click "Confirm." Java analogy: the Console is `java -jar` with a friendly GUI wrapper; the CLI is invoking the Java class directly via `ProcessBuilder` — same JVM, full programmatic control. For QA engineers, the operational consequence is concrete: a pipeline that uploads 200 Selenium screenshots to S3 after a test run needs one `aws s3 sync` command, not 200 manual drag-and-drops — and if that command is not in the pipeline script, the screenshots disappear when the CI agent resets.

Step 1 — Create an AWS Account

Enable MFA (Multi-Factor Authentication) on your root account immediately after creation. Go to IAM → Security credentials → Activate MFA.

Step 2 — Install AWS CLI

Why Is the aws --version Output the ONLY Proof of Installation?

winget/brew/curl download the AWS CLI…

`winget install Amazon.AWSCLI` (or brew/curl) DOWNLOADS the AWS CLI binary and ADDS it to PATH — but it hasn't CONNECTED to any AWS resource yet.

aws --version proves the terminal's PATH…

`aws --version` is the ONLY command that proves the terminal's PATH can FIND this NEW command and the binary runs WITHOUT being corrupted — it does NOT involve authentication yet.

A "command not found" error is USUALLY…

A "command not found" error USUALLY does NOT mean the install FAILED — it means the terminal session hasn't RE-READ the PATH change yet; RESTARTING the terminal is usually the FIX.

Expected output: aws-cli/2.15.0 Python/3.11.6 Windows/10 exe/AMD64 prompt/off

Step 3 — Create IAM User & Access Keys

Step 4 — Configure AWS CLI