I have tried installing awscli using pip, anyways with msi installer its working, but i just want to inform you, pip would be convienient for me if people want to write batch files for windows
C:\Users\vasubabu.k>python --version
Python 3.6.4
C:\Users\vasubabu.k>pip --version
pip 9.0.1 from c:\users\vasubabu.k\appdata\local\programs\python\python36\lib\site-packages (python 3.6)
C:\Users\vasubabu.k>pip install awscli
Requirement already satisfied: awscli in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages
Requirement already satisfied: colorama<=0.3.7,>=0.2.5 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from awscli)
Requirement already satisfied: rsa<=3.5.0,>=3.1.2 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from awscli)
Requirement already satisfied: botocore==1.9.3 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from awscli)
Requirement already satisfied: docutils>=0.10 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from awscli)
Requirement already satisfied: s3transfer<0.2.0,>=0.1.12 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from awscli)
Requirement already satisfied: PyYAML<=3.12,>=3.10 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from awscli)
Requirement already satisfied: pyasn1>=0.1.3 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from rsa<=3.5.0,>=3.1.2->awscli)
Requirement already satisfied: python-dateutil<3.0.0,>=2.1 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from botocore==1.9.3->awscli)
Requirement already satisfied: jmespath<1.0.0,>=0.7.1 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from botocore==1.9.3->awscli)
Requirement already satisfied: six>=1.5 in c:\users\vasubabu.k\appdata\roaming\python\python36\site-packages (from python-dateutil<3.0.0,>=2.1->botocore==1.9.3->awscli)
later i added aws cli executable to system path
C:Usersvasubabu.kAppDataLocalProgramsPythonPython36Scripts
then i checked for aws command
```
C:Usersvasubabu.k>aws
'aws' is not recognized as an internal or external command,
operable program or batch file.
'''
Adding the Scripts
directory to the path is part of the setup of using pip and Python on Windows and there isn't a whole lot AWS CLI can do about it. However, not having aws
after you added it to the path I believe is wrong. Did you try closing your command prompt after adding to the path and perhaps logging in and out? I forget what Windows requires to update the working$PATH
after a change.
hello mr donald i have done whatever ever i have mentioned in you docs. Even re opening the command prompt windows. I wouldnr have raised this issue on github without atleast knowing restarting cli on windows after new installation. anyway you are always welcome to connect to my system to verify. sorry if i troubled you!
i remember the 6th point
The issue is that %USERPROFILE%\AppData\Local\Programs\Python\Python36\Scripts
points to C:\Users\[USER]\AppData\Local\Programs\Python\Python36\Scripts
whereas aws.cmd is at C:\Users\[USER]\AppData\Roaming\Python\Python36\Scripts\aws.cmd
So the documentation is wrong, you should add %APPDATA%\Python\Python36\Scripts
to the PATH (or the PIP installer installs it in the wrong place.)
I too have this issue on Windows. I have the path set as indicated, C:Users{USERNAME}AppDataRoamingPythonPython34site-packagesawscli which is where it was installed. But there is no AWS.cmd on the drive.
I also tried installing using the windows installer MSI package, and it installs AWS.cmd to program files, however the json template handling throws errors and I know there's no issue with the json. Some definite wonkyness going on here.
EDIT: after uninstalling the msi package version, and pip uninstall awscli
, I was able to reinstall using pip install awscli
(omitting --user) and it worked. There might be an odd installation glitch here.
Still have issues running aws ses create-template --cli-input-json file://Template.json
but I'll post that in a new issue.
Thansk @replaysMike, it works for me!
I used pip for Python 3.4. aws.cmd was found in C:UsersVikasAppDataRoamingPythonScripts.
How did I find it? I ran 'pip uninstall awscli' and it showed me all the files it will delete along with the confirmation.
@replaysMike same issue for me! weird
Yes, as mentioned by @matyasforian , add the path C:Users[user]AppDataRoamingPythonScripts to environment variables and then it works. Worked for me. Thanks
I did something similar to perfenginner0321. I found that awsebcli installed in the C:.....AppDataRoaming... while my $PATH for python was C:.....AppDataLocal...
I copied the Scripts and site-packages folders from the ...RoamingPythonPython37 to the local version and it all is working well now.
Most helpful comment
The issue is that
%USERPROFILE%\AppData\Local\Programs\Python\Python36\Scripts
points toC:\Users\[USER]\AppData\Local\Programs\Python\Python36\Scripts
whereas aws.cmd is atC:\Users\[USER]\AppData\Roaming\Python\Python36\Scripts\aws.cmd
So the documentation is wrong, you should add%APPDATA%\Python\Python36\Scripts
to the PATH (or the PIP installer installs it in the wrong place.)