-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not able to install Amplify CLI #13290
Comments
Hey @ZhengHuang-git, thank you for reaching out. you will have to use npm: |
Hi @ykethan
I also tried " curl -sL https://aws-amplify.github.io/amplify-cli/install | bash && $SHELL ". I saw the following error.
Do you have any other suggestions? Thanks in advance, |
Hey @ZhengHuang-git, from the EACCES error message and the information here . It appears you will need to change npm's default directory to point to home directory. Additionally, curious on the use case on using AWS CloudShell to install Amplify CLI. Could you provide us some additional information on this. |
Hi @ykethan , I just started to learn AWS by following the AWS' online tutorial (https://aws.amazon.com/getting-started/hands-on/host-static-website/) which says to use Amplify in AWS console. It appears that AWS console is different from AWS CloudShell. Do you have any info on how to access AWS console? |
Hey @ZhengHuang-git, sure no worries. The services such as AWS Cloudshell, AWS Amplify console are part of the AWS console. The tutorial guides you in hosting a static website on the AWS Amplify console.
if you have any additional questions please do let us know. |
Closing the issue due to inactivity. |
|
Amplify CLI Version
Trying to install Amplify CLI
Question
Hello Everyone,
I am trying to install the Amplify CLI with the following command from the CloudShell.
curl -sL https://aws-amplify.github.io/amplify-cli/install-win -o install.cmd && install.cmd
But I got this this error -> " -bash: install.cmd: command not found "
Can anyone tell me what I am missing?
Thanks in advance,
Zheng
The text was updated successfully, but these errors were encountered: