Git bash will not resolve "sam" command

Question

I am using Win10 latest. After installing AWS-SAM-CLI and testing the installation with:

sam --version

I get the message

bash: sam: command not found

however, when I use Powershell, cmd or ConEmu they can all resolve "sam".

the path is "e/Program Files/Amazon/AWSSAMCLI/bin" but other commands like "yarn" work fine which is also installed at "e/Program Files/..."

Any ideas? Thanks

You can use `alias sam="sam.cmd"` if it works in normal cmd. Now `sam --version` should work. — Nikolai, Mar 19 '21 at 12:17
it can also be set to create the alias on terminal open, like with `echo 'alias sam="sam.cmd"' >> ~/.bashrc` for e.g. ; some more thoughts on that [here](https://superuser.com/questions/602872/how-do-i-modify-my-git-bash-profile-in-windows?newreg=11a9bb92102040fc83225f509c48b46f) — mud, Jul 04 '23 at 12:15

score 36 · Accepted Answer · answered Jul 23 '20 at 19:09

36

sam.cmd --version

The windows version of the SAM CLI does not have a direct executable binary. It is instead a .cmd script that echos your options to the python executable.

@rem
@echo off

setlocal

"%~dp0/../runtime/python.exe" -m samcli %*

I haven't figured out how to make it work with

sam --version

My assumption is that powershell and command prompt see .cmd as an executable not requiring an extension where git bash does not.

answered Jul 23 '20 at 19:09

James Pickett

476
4
3

6

You can make it work without the .cmd extension by adding an alias in your .bashrc: https://stackoverflow.com/a/50391166/1429439 – C.M. Aug 19 '20 at 15:56
3

The fact that this is not in docs for installation is annoying – Maxqueue Nov 13 '20 at 05:24
8

Thanks @C.M. I literally just did `alias sam='sam.cmd'`, and it's working great. :) – isaacsan 123 Nov 02 '21 at 09:57

score 23 · Answer 2 · answered Mar 05 '21 at 19:22

23

Here is how I got it work with an alias. alias sam="/c/Program\ Files/Amazon/AWSSAMCLI/bin/sam.cmd"

answered Mar 05 '21 at 19:22

Clinton White

231
2
2

While the alias worked when invoking sam straight from the command line it wouldn't work in scripts. After following the above step to make them work in scripts use 'sam.cmd' instead of 'sam' – Arafat Nalkhande Jul 02 '22 at 01:24
where are you adding the alias? in vs code or somewhere else? – spacedog Jul 21 '22 at 19:22
Just run this in the cli (i.e. git bash) – FelixRe_ Jan 15 '23 at 12:07

score 7 · Answer 3 · edited Apr 18 '22 at 03:08

7

$ vi ~/.bashrc  # or favorite editor

Add:

alias sam='sam.cmd'

Then:

$ source ./.bashrc # can use '. ./.bashrc

edited Apr 18 '22 at 03:08

Ethan

876
8
18
34

answered Apr 07 '22 at 18:00

SpiesInOrbit

81
1
1

score 3 · Answer 4 · answered Aug 11 '21 at 13:13

While the alias worked when invoking sam straight from the command line it wouldn't work in scripts that I was using.

To fix this for both instances I found that I needed to add a shell script equivalent of the installed .cmd script, named sam, in the same folder as it, typically C:\Program Files\Amazon\AWSSAMCLI\bin:

#!/bin/sh
basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")

case `uname` in
    *CYGWIN*|*MINGW*|*MSYS*) basedir=`cygpath -w "$basedir"`;;
esac

"$basedir/../runtime/python.exe" -m samcli "$@"
ret=$?
exit $ret

score 0 · Answer 5 · answered Mar 29 '23 at 13:56

Try uninstalling and reinstalling the SAM CLI. You can do this by running the following commands:

pip uninstall aws-sam-cli
pip install aws-sam-cli

Check the version of Python you're using. The SAM CLI requires Python 3.6 or later. You can check your Python version by running the command python --version. If you're using an earlier version of Python, you'll need to upgrade to a later version.

Git bash will not resolve "sam" command

5 Answers5