-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No credentials set for components during deploy #896
Comments
@daaru00 I'm unable to reproduce this. Which component are you using? It seems from what you're describing that you're running your own component? could you provide more context here? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
After a few months I didn't deploy anything and updated to the latest version (3.7.1) I cannot able to deploy any components due an AWS SDK authentication error.
Every component seems to be unable to authenticate, in my
.env
I set AWS_PROFILE but didn't works:Tried to set the environment variable before deploy command, unfortunately same result:
Using AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in
.env
results in a warning message:I follow the instruction, deployed the CloudFormation Stack, setup the "default" provider for my org, set the SERVERLESS_ACCESS_KEY (already set in previous tests) and tried to re-deploy but it still doesn't solve.
For every tests I used a modified component in "dev" version with some debug log and a STS GetCallerIdentity API call that returns a different account number that mine:
also
this.credentials
in Serverless Component is an empty object, therefore seems no authentication is performed or the role set by the provider is not assumed correctly.I've no errors or warning during deploy, even using the "--debug" flag.
Maybe I've just misunderstood the new documentation about credentials, however, it seems strange to me that none of the configurations I have tried are not working.
Additional Data
The text was updated successfully, but these errors were encountered: