The first time your AWS CLI command returns less data than expected, you feel it. A silent gap. No error. Just missing pieces.
AWS CLI data omission happens more than most realize. You run a command, you trust the output, you move on. But sometimes that output is incomplete. The reasons range from pagination limits to filters you forgot were active, to permissions that quietly cut chunks out of your results. AWS won’t always warn you. If you don’t know what to look for, you ship decisions based on partial truths.
The most common culprit is pagination. Many AWS CLI commands only return a set number of results per call. If you don’t use the --max-items or --starting-token flags correctly, you only see what fits in that slice. Another silent factor is filtering. Passing a filter flag trims results at the source, but so can defaults you didn’t set yourself. There’s also IAM. When your credentials don’t have permission to see certain resources, AWS simply omits them—no markers, no placeholders, just absence.