Checking the installed AWS CLI version confirms which client build the current shell is actually running before troubleshooting command differences, comparing automation behavior across hosts, or deciding whether an upgrade is still needed.
The aws --version command prints a single local version line and does not require configured credentials or network access. The first aws-cli/x.y.z token identifies the CLI release, while the remaining fields show the bundled runtime and platform details for that binary.
AWS CLI version 2 and version 1 use the same aws command name, so more than one install can exist on PATH at the same time. AWS documents version 2 as the current major release and version 1 as the older line, so an unexpected aws-cli/1.x result is a reason to check which binary the shell resolved before reinstalling or changing scripts.
$ aws --version aws-cli/2.34.32 Python/3.14.4 Darwin/25.4.0 source/arm64
No credentials or region are required for this command because it only reports the local client build.
v2 example: aws-cli/2.34.32 Python/3.14.4 Darwin/25.4.0 source/arm64 v1 example: aws-cli/1.44.81 Python/3.14.4 Linux/6.8.0-57-generic botocore/1.42.91
aws-cli/2.x means AWS CLI v2, while aws-cli/1.x means the older AWS CLI v1 line.
$ command -v aws /usr/local/bin/aws
On Windows, use where aws in Command Prompt or Get-Command aws in PowerShell to inspect the active executable path.
$ type -a aws aws is /usr/local/bin/aws aws is /opt/homebrew/bin/aws
The first match wins, so an older install that appears earlier on PATH can answer even when a newer copy is also installed.
$ aws --version aws-cli/2.34.32 Python/3.14.4 Darwin/25.4.0 source/arm64
After the version matches the expected install, make one signed request to confirm that the shell is also using the intended credentials. Related: Check the current caller identity