Software Version (does not seem relevant for the issue)
Mac Sonoma 14.4.1 (23E224)
Node v21.7.3
npm 10.5.2
Steps to reproduce:
Run AWS Configure
Set AWS Access Key ID as your desired value
Set AWS Secret Access Key your desired value
Set AWS Region to a typo e.g: ^A (CTRL+A)
Fresh install of SST and create new project
Run sst dev
OP: Now that I understand the root cause of what was causing my issue was an invalid AWS Configuration because of a typo, alternatives, and similar errors are produced when using valid string values but that are still invalid aws Zones e.g
Following steps to reproduce but using test as a AWS region
You might get this output:
Error initializing aws:
operation error SSM: GetParameter, https response error StatusCode: 0, RequestID: , request send failed, Post "https://ssm.test.amazonaws.com/": dial tcp: lookup ssm.test.amazonaws.com: no such host
// LOG:
ERROR msg="exited with error" err="Error initializing aws:\n operation error SSM: GetParameter, https response error StatusCode: 0, RequestID: , request send failed, Post \"https://ssm.test.amazonaws.com/\": dial tcp: lookup ssm.test.amazonaws.com: no such host"
What solved the issue for me
In case it was not clear, this was solved by setting the AWS Region to a valid value such as us-east-1 in case it helps you out to quickly get you out of this problem.
Actions Required (?)
I'm unsure if this issue deserves any action but @jayair mentioned that probably we could handle this better as the error is pretty opaque, from my perspective, I was entirely sure that my aws config was good as I was looking at the wrong .aws/credentials file and at the end a very basic error put me off track.
not entirely sure how best to handle this because there isn't a good way for us to catch this. we could have a list of regions we know aws supports but wondering if that will be brittle
Context:
Discord Thread The first time setup with SST/Ion was trying to follow up the examples on https://ion.sst.dev/docs/start/aws/api/ and the
sst dev
command was throwing an error:as Text
Log:
SST Version
Software Version (does not seem relevant for the issue)
Steps to reproduce:
sst dev
OP: Now that I understand the root cause of what was causing my issue was an invalid AWS Configuration because of a typo, alternatives, and similar errors are produced when using valid string values but that are still invalid aws Zones e.g
Following steps to reproduce but using
test
as a AWS region You might get this output:What solved the issue for me
In case it was not clear, this was solved by setting the AWS Region to a valid value such as
us-east-1
in case it helps you out to quickly get you out of this problem.Actions Required (?)
I'm unsure if this issue deserves any action but @jayair mentioned that probably we could handle this better as the error is pretty opaque, from my perspective, I was entirely sure that my aws config was good as I was looking at the wrong
.aws/credentials
file and at the end a very basic error put me off track.