Every subcommand, every flag, every output format is a door. But most stay closed because discovery is harder than it should be. You shouldn’t need to memorize 200 pages of docs to run one powerful command. You need a way to see what’s possible, fast.
AWS CLI discoverability is about speed, precision, and control. It’s knowing that aws s3 cp has hidden options that can save hours. It’s realizing the CLI has tab completion, built-in help, and structured output—yet most workflows ignore it. The problem isn’t the tool. The problem is finding what matters before you lose the context of the work.
The CLI is an API in your terminal. It connects to over 200 AWS services. But without discoverability, it turns into endless trial-and-error. You flip between browser tabs, JSON dumps, and commands you half-remember. It costs time. It drains momentum. It lowers the ceiling of what you can build.
Good discoverability collapses steps. The moment you type aws ec2 you should see all available actions. The moment you know an action, you should know its parameters. Output should be searchable, parseable, and easy to reuse in scripts or pipelines. When the CLI becomes self-explanatory, adoption soars and friction drops.