AWS CLI — ECR & Containers Cheat Sheet 2026
AWS CLI ECR & Containers Cheat Sheet is the complete quick-reference of AWS CLI ECR & Containers commands grouped by function. Copy any command with one click and find what you need with Ctrl+F in under 3 seconds.
ECR & Containers
| Action | Command | Useful flags |
|---|---|---|
| Authenticate Docker with the default registry (username is AWS) |
|
--region --username --password-stdin |
| Create a repository |
|
--repository-name --image-scanning-configuration --region |
| Tag a local image for ECR |
|
|
| Push an image to a repository |
|
|
| Pull an image from a repository |
|
|
| Delete an image from a repository |
|
--repository-name --image-ids |
| Delete a repository |
|
--repository-name --force |
| List images within a repository |
|
--repository-name |
⚠️ Dangerous / Destructive Commands
These commands are irreversible. Verify your environment (dev/staging vs prod) before running them.
| Action | Command | Warning |
|---|---|---|
| ⚠️ Ecr batch-delete-image |
|
Irreversible — verify the target before running |
| ⚠️ Ecr delete-repository |
|
Irreversible — verify the target before running |
FAQ — Frequently Asked Questions
What is the difference between ECR & Containers and the other groups?
Each group in this AWS CLI cheat sheet covers a distinct area. ECR & Containers focuses on its specific scope, while the other groups and the remaining groups cover networking, storage, security and diagnostics respectively.
How do I check the installed AWS CLI version?
Run the version command (usually aws version or aws --version). The output shows the client and, when applicable, the server version.
Why does AWS CLI return ‘permission denied’?
A ‘permission denied’ error in AWS CLI usually means the current user lacks sufficient privileges or credentials are not configured. Check: (1) assigned IAM/RBAC roles, (2) an active authentication context via the corresponding login command.
How do I filter AWS CLI output by status or name?
Use flags such as --filter, --selector or --query depending on the tool. You can also pipe into grep or jq to process JSON:
aws list | grep RUNNING
What is the fastest way to debug a AWS CLI error?
Add the verbose flag (--verbose, -v or --debug) to the failing command. This reveals the underlying HTTP/API calls and the full error response body.
Official sources & references
Commands cross-checked against vendor documentation and high-authority repositories: