AWS CLI Cheat Sheet — MyAdminDesk

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

AWS CLI Cheat Sheet is a reading list for AWS CLI. The generator drafts one resource and says to review before apply. Replace account IDs, images, and sample passwords.

Do not apply from this sheet. An ingress of 0.0.0.0/0 is a line you delete. A sample password is replaced.

The browser tool drafts text. It does not log in.

192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.

The change you can finish

Apply nothing while you are writing the note. When the lab window opens, it is one change on the account named in the ticket. Read the draft, then the account, then decide.

Rollback is the previous file, the previous plan, or the lab resource you can delete because it was only a lab.

Confirm the account you administer.
Read one command or one resource the ticket names.
Replace placeholders and sample passwords.
Delete an ingress of 0.0.0.0/0.
Do not apply from this sheet.
Hand a create to the how-to for that resource.

Mistakes that outlive the statement

AWS CLI commands goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Applying a draft you did not read.
The wrong account.
A secret, an access key, or a kubeconfig in git.
Two changes in one window.
No copy saved before the change.
A documentation address or example.com left in a file you apply.
An ingress from 0.0.0.0/0 left in the file.
Calling the generator output a finished production change.
Applied because the command was short.

Decisions to write down

One decision for AWS CLI commands: This sheet is for reading. The account is yours. Nothing was applied. No secret is in the note. And the how-to owns any create.

Checks before you call it done

Confirm this before you call the change done: The account is written. One draft was read. Nothing was applied. No secret is in the note. And the next action is a named how-to, or a stop. If one of those fails, stop.

# Read first. Apply later, from the how-to.
# Review before apply.
# AWS CLI.
# 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep. 10.0.0.0/16 is a sample prefix, not a network you publish unless you already use it.

Before you leave the account

AWS CLI Cheat Sheet ends when the account in the note is the account in the ticket. If it is not, stop.

The draft stays a draft until a person has read the names in it. A generator does not log in, does not apply, and does not scan.

prompt-for-this is a reminder that a secret is missing. It is not an access key, a token, or a password you save. An Azure secret draft may contain a sample password. Replace it. Do not file it.

One change is the window. If two things move and the result is wrong, you will not know which one did it.

If the same step fails twice, stop for the day. Restore the copy you took first.

A second person reads the account and the change aloud. If they cannot find them in the ticket, the note is not done.

This page is a planning guide. It is not a vendor manual, not an official standard, not legal advice, and not an audit opinion. You do not apply it against an account you do not administer.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Multi-Cloud CLI Guide

More in this cluster

The pillar for this page, and the next published pages filed with it.