AWS CLI: Most Useful Commands Cheat Sheet (2026)

The AWS CLI is more than just a way to interact with AWS; it’s a powerful scripting engine that lets you manage your cloud infrastructure with the precision of code.

Let’s see it in action. Imagine you need to find all EC2 instances in your us-east-1 region that are running and have a specific tag, say Environment: Production.

aws ec2 describe-instances \
  --region us-east-1 \
  --filters "Name=instance-state-name,Values=running" "Name=tag:Environment,Values=Production" \
  --query "Reservations[*].Instances[*].InstanceId" \
  --output text

This command, when executed, will churn through your AWS account and return a plain text list of just the instance IDs that match your criteria. No fancy dashboards, no clicking around – just pure, actionable data.

The problem the AWS CLI solves is the inherent complexity and scale of cloud environments. Manually managing hundreds or thousands of resources through a web console is not only tedious but also error-prone. The CLI provides a programmatic interface, allowing for automation, repeatable tasks, and integration into CI/CD pipelines. It abstracts away the HTTP requests and JSON payloads, presenting a more human-readable syntax for interacting with AWS services.

Internally, the AWS CLI is a Python application. When you run a command like aws s3 ls, it’s not just a simple alias. The CLI parses your command, determines the AWS service and API call (in this case, S3 and ListBuckets), constructs the necessary request with your credentials and region, sends it to the AWS API endpoint, and then processes the JSON response, formatting it according to your --output specification.

The levers you control are numerous. The --query parameter, for instance, uses JMESPath, a powerful query language for JSON. This allows you to filter, transform, and shape the output of any AWS CLI command. You can select specific fields, flatten nested structures, and even perform basic calculations. Then there’s --output, which can format results as json (the default), text, or table. Combined with --query, this makes the CLI incredibly versatile for data extraction and manipulation.

Consider the --generate-cli-skeleton command. It’s a hidden gem that lets you generate template JSON files for complex API calls that require input bodies. For instance, to create an SQS queue with specific attributes, you might not know the exact JSON structure.

aws sqs create-queue --generate-cli-skeleton

This outputs a JSON structure like:

{
  "QueueName": "string",
  "Attributes": {
    "string": "string"
  },
  "tags": {
    "string": "string"
  }
}

You can then fill in the values, save it as create-queue-params.json, and run the actual command:

aws sqs create-queue --cli-input-json file://create-queue-params.json

This bypasses the need to constantly consult API documentation for the correct syntax of request bodies, significantly speeding up the process of crafting complex commands.

The next hurdle to overcome is mastering service-specific paginated responses, where AWS returns results in chunks.