Stop Clicking
The AWS Console is great for exploration and learning, but professional cloud engineering happens in the terminal and in code. Think of the Console as a car's dashboard — useful for monitoring and occasional adjustments, but you wouldn't use it to build the car itself. The CLI and SDK are the assembly line.
- AWS CLI (Command Line Interface): A command-line tool for interacting with AWS services directly from your terminal. Used for ad-hoc administration, shell scripts, and automation pipelines.
- AWS SDK (Software Development Kit): A language-specific library for building applications that talk to AWS. Examples include Boto3 for Python, the AWS SDK for JavaScript (v3), and the AWS SDK for Java.
The CLI is built on top of the Python SDK (Boto3) internally — so understanding one helps you understand the other.
Why This Matters
Every serious AWS workflow — infrastructure provisioning, CI/CD pipelines, automated backups, cost reporting — relies on the CLI or SDK. The Console cannot be scripted. The CLI and SDK can. Mastering their setup is the prerequisite for everything else in platform engineering.
Installation at a Glance
The AWS CLI v2 is a standalone binary. Install it without needing Python:
# macOS (Homebrew)
brew install awscli
# Linux (x86_64)
curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install
# Verify
aws --version
# aws-cli/2.x.x Python/3.x.x ...
Boto3 is installed via pip:
pip install boto3
boto3.__version__ # verify in Python REPL
Interviewers sometimes ask: "What's the difference between the AWS CLI and the AWS SDK?" The precise answer: the CLI is a user-facing command-line tool for humans and shell scripts; the SDK is a library for embedding AWS API calls inside application code. Both ultimately call the same AWS REST APIs, but the SDK gives you programmatic control over request construction, retry logic, pagination, and response parsing — things the CLI abstracts away.