Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
exec: "aws": executable file not found in $PATH
See original GitHub issueWhen running sam package I get exec: "aws": executable file not found in $PATH.
$ command -v aws
/Users/<username>/Library/Python/3.6/bin/aws
Invoking aws directly seems to work as expected. Globally installed on a Mac (with nvm).
Please let me know if you have any ideas or if I can provide additional information.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
executable file not found in $PATH when trying to connect to a ...
Check which shell is installed in your image/container. sudo docker exec -it [cid] echo $SHELL. If above command returns /bin/bash, ...
Read more >Troubleshooting AWS CLI errors - AWS Command Line Interface
Command not found errors. This error means that the operating system can't find the AWS CLI command. The installation might be incomplete or...
Read more >awscli build step fails with command not in path error
Error: Unable to locate executable file: 'aws'. Please verify either the file path exists or the file can be found within a directory...
Read more >How to fix docker error executable file not found in $PATH?
Make sure the script my-custom-script.sh is available - the First check which you should perform is by checking the shell script my-custom- ...
Read more >Elastic Agent on Amazon Linux 2: "service" executable file not ...
Error: failed to start service (elastic-agent): "service" failed: exec: "service": executable file not found in $PATH For help, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had the exact same issue, with the same symptoms. I was able to resolve by doing a pip uninstall awscli, then I did a brew update, then brew install awscli and the problem was resolved
It worked for me just that I had to
brew link --overwrite awsclito link the awscli installed by the brew