Troubleshooting: aws Command Not Recognized in Windows After Adding Path to Environment Variables

Below are the environment variables I have set for the PATH:
Solution 1:
After extensive effort, I discovered that I had overlooked a necessary additional PATH entry in order to successfully run on Windows.
Note:
If you are using a Windows machine, the CLI is typically installed in either C:Program FilesAmazonAWSCLI (64-bit version) or C:Program Files (x86)AmazonAWSCLI (32-bit version) by default.

Question:

In accordance with instructions found in various sources, I appended ‘%USERPROFILE%AppDataRoamingPythonPython37Scriptsaws’ to the Path variable, testing both with and without the inclusion of aws at the end.

Despite clicking OK everywhere and restarting the CLI, I am still encountering the message “‘aws’ is not recognized as an internal or operable program” when I type aws at the command prompt (I did restart it after updating the path). Do you have any suggestions for what I might be overlooking?


Solution:

If this is on a Windows machine, the CLI will be installed to either C:Program FilesAmazonAWSCLI (64-bit version) or C:Program Files (x86)AmazonAWSCLI (32-bit version) by default. Therefore, it seems that the PATH you have added is incorrect.
“””.

Please visit the following link for guidance on how to install AWS CLI on Windows: https://docs.aws.amazon.com/cli/latest/userguide/install-windows.html#awscli-install-windows-path.

run the command – where aws

After locating the installation location, simply copy it and add it to your path. I trust this information is beneficial to you.

Frequently Asked Questions