https://serverless-stack.com/ logo
Join Slack
Powered by
Hi all, has anyone seen this error when building? ...
# help
j
Hi all, has anyone seen this error when building? SST version 0.63.0
Copy code
EnvironmentCredentialsProviderFailure: Variable AMAZON_ACCESS_KEY_ID not set.
I'm only seeing it in the ci pipeline, where I've only set 
AWS_ACCESS_KEY
and 
AWS_SECRET_KEY
t
this may be weird but can you make a blank 
~/.aws/credentials
file in your ci env?
need to see if it's the same bug
j
There's no 
~/.aws/credentials
in the pipeline
t
Yeah I know I'm saying can you make an empty file there
I had this same issue locally and it went way when I did that
j
Ah got it. I see what you mean. I'll check now. Thanks!
Creating an empty 
~/.aws/credentials
fixes the above issue, now getting:
Copy code
ProcessCredentialsProviderFailure: Profile default not found
I'm pushing a test to add default dummy credentials
Yep, looks like it's trying to use the credentials file when it doesn't find 
AMAZON_ACCESS_KEY_ID
and 
AMAZON_SECRET_ID
t
@Frank I think you might have an idea about what's going on here
j
Don't want to send you down a rabbit hole. Could have been a weird issue in the pipeline. Created a different pipeline from scratch and it works now. Thanks for the help!
f
@J. T. Garcia are 
AWS_ACCESS_KEY
 and 
AWS_SECRET_KEY
set by u? Can u name them to 
AMAZON_ACCESS_KEY_ID
 and 
AMAZON_SECRET_ID
?
j
Hi, sorry for the late reply. Been out for a few days. I did change them to 
AMAZON_ACCESS_KEY_ID and AMAZON_SECRET_ID
and it worked.
f
No worries. Glad it’s working!
Open in Slack
PreviousNext
Powered by