Open schambers-slate opened 2 weeks ago
This is actually caused by not having an sso token locally. The error message isn't too indicative. I solved it by refreshing my sso token via aws sso login
I'm going to leave the issue open for now as the error message should really be refined to indicate that this is the potential issue
Hi @schambers-slate, Thanks for raising this issue! This seems to be a bug coming from the boto3 client since we do have error handling for errors coming from fetching the account id. Ill try to reproduce this locally and see if i can find the exact behaviour
Thanks @sidhujus, If you need me to try to replicate again I can do so as well. Let me know.
Description:
Running any sam local commands results in this error. Randomly started happening yesterday and I'm unable to run
sam local
I'm unable to run any sam commands locally included sam local start-api, sam local invoke, etc. All cli commands with sam local result in same output below.
It seems as if there's some local cache thats tripping up sam cli but I'm unable to find this cache if it exists
Steps to reproduce:
Create a new project via sam init run sam local start-api
Observed result:
Expected result:
sam to invoke lambda function locally
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
M1 Mac
sam --version
: SAM CLI, version 1.126.0Add --debug flag to command you are running
Provided above