Why does AWS show a long json file with no human readable output flag?

[TheKevinWang]

So I tried to list VMs with aws ec2 describe-instances and I get this massive json file. In azure powershell, I would get a human readable table, but with the same level of fidelity as the aws json file, because they are objects. Why isn't there a --table or --human-readable flag for everything aws (I'm sure this isn't the only issue)? Seems like the azure powershell method is simply superior. Maybe they should release aws powershell.

Guide suggests using jq query with --query. What a terrible idea in terms of usability lol. Imagine remembering and typing all this out all this just to do something as simple as list VMs.
https://docs.aws.amazon.com/cli/latest/userguide/cli-services-ec2-instances.html

EDIT: turns out there is aws powershell, but it sucks

PS > Get-EC2Instance -ProfileName '<>' -debug 
DEBUG: Credentials obtained from stored profile named '<>'
DEBUG: Region obtained from stored region with value '<>'
VERBOSE: Invoking Amazon Elastic Compute Cloud (EC2) operation 'DescribeInstances' in region '<>'

Confirm
Continue with this operation?
[Y] Yes  [A] Yes to All  [H] Halt Command  [S] Suspend  [?] Help (default is "Y"): Y
Get-EC2Instance: The response ended prematurely.