In Day 06, I start with the basics of AWS CLI (Command Line Interface) and why you’d even use it when the AWS Console UI already exists. The point is simple: there are many scenarios where you don’t want to click around in the UI—you want to manage AWS resources from the terminal, and even automate workflows using scripts. I show you how to verify whether AWS CLI is installed using commands like `aws help` and `aws --version`, and then I walk you through installing AWS CLI v2 on Windows (same docs exist for Mac/Linux as well). After installation, I make it very clear: you’re still not ready. AWS CLI needs authentication. When you run something like `aws s3 ls`, you’ll hit “unable to locate credentials”, and that’s where `aws configure` comes in. I explain exactly what the CLI asks for (Access Key ID, Secret Access Key, default region, output format) and how to create access keys from IAM security credentials—plus the security warning: don’t leak keys, and remember you only see the secret once. Finally, we go hands-on: creating and deleting an S3 bucket from the CLI (`mb` and `rb`), and then moving into EC2 basics—creating a key pair, finding an AMI ID (via console or CLI), running `describe-instances`, filtering output, and terminating instances so you don’t get billed. This is the real power of CLI: fast, scriptable, and practical.