Unknown options: -G on MacOS

[Mr-Smu]

Describe the bug

% sw_vers
ProductName: macOS
ProductVersion: 15.7.2
BuildVersion: 24G325
% aws --version
aws-cli/2.32.3 Python/3.13.9 Darwin/24.6.0 exe/x86_64
% aws s3 ls help

Unknown options: -G
% aws s3 cp help <= WORKS FINE
% aws s3 mv help <= WORKS FINE
etc...

% aws s3api list-buckets
None
BUCKETS arn:aws:s3:::mybucket1.etc.etc...
BUCKETS arn:aws:s3:::mybucket2.etc.etc...
BUCKETS arn:aws:s3:::mybucket3.etc.etc...
OWNER xxxxxxxxxxx...

% aws s3 ls

Unknown options: -G
%

Same results with:
% sw_vers
ProductName: macOS
ProductVersion: 26.1
BuildVersion: 25B78
% aws --version
aws-cli/2.32.3 Python/3.13.9 Darwin/25.1.0 exe/arm64

Any thoughts?

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

There is no -G option so the 'ls' command should work.

Current Behavior

Unknown options: -G even though option -G was not used.

Reproduction Steps

See bug description.

Possible Solution

Fix the bug?

Additional Information/Context

First time setting up AWS CLI and it looks like I have come across a bug with the 'ls' command. I spent hours troubleshooting this.

CLI version used

aws-cli/2.32.3 Python/3.13.9 Darwin/25.1.0 exe/arm64 (and x86_64_

Environment details (OS name and version, etc.)

macOS 26.1 and macOS 15.7.2

[adev-code]

Hello @Mr-Smu, thanks for reaching out. I have tried from the same machine using MacOS and I did not get the same issue: Unknown options: -G. Generally, this error would happen if an unknown parameter is passed by a user or the local machine shell. Please ensure your local shell don't have some sort of wrapper or aliases that could be appending a parameter. Also can you add --debug and the Arguments entered to CLI on the logs would show?

[Mr-Smu]

Hi Adev-code, so turns out I do have an alias "ls='ls -G'". I was not aware that an alias can affect parameters passed to a command. I'm not sure how that works but I guess the issue is solved. Thank you for your help.

[adev-code]

More than welcome! Closing.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.