serverless: 1.48.1 gives Credentials error.
This is a Bug Report
Description
-
What went wrong?
- Get this error now when deploying through an AWS pipeline:
Serverless Error ---------------------------------------
Could not locate deployment bucket. Error: AWS provider credentials not found. Learn how to set up AWS provider credentials in our docs here: <http://bit.ly/aws-creds-setup>.
Our set up uses a serverless.yml file to deploy stacks. The pipeline were successfully building before the release of 1.48.1. I verified that this was an issue with serverless by installing 1.48.0 instead of the latest release using this command: npm install -g serverless@1.48.0. When I use 1.48.0 the builds pass as expected.
- What did you expect should have happened?
- I expected the build to pass
- What was the config you used?
- What stacktrace or error message from your provider did you see?
Similar or dependent issues:
Additional Data
- Serverless Framework Version you’re using: 1.48.1
- Operating System:
- Stack Trace:
- Provider Error messages:
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 22
- Comments: 26 (5 by maintainers)
Commits related to this issue
- Block npm:serverless@1.48 https://github.com/serverless/serverless/issues/6414 — committed to seek-oss/rynovate by 72636c 5 years ago
- Fix #6414 by checking for ecs metadata — committed to serverless/serverless by dschep 5 years ago
- Fix #6414 by checking for ecs metadata — committed to serverless/serverless by dschep 5 years ago
- Fix #6414 by checking for ecs metadata — committed to serverless/serverless by dschep 5 years ago
- Fix #6414 by checking for ecs metadata — committed to serverless/serverless by dschep 5 years ago
- Fix #6414 by checking for ec2 metadata (#6427) Fix #6414 by checking for ec2 metadata — committed to serverless/serverless by dschep 5 years ago
Run into the same problem in codebuild.
I think we shouldn’t force to use AWS keys in order to deploy serverless apps.
in codebuild, I have managed role which has the right access for deployment without using any AWS keys.
I am having the same issue
Encountered this issue today using 1.48.2. We can temporarily stick with 1.48.0 but this should be resolved as soon as possible.
This is a pretty major bug that will block a lot of CD pipelines that we have setup. Is there a timeframe of when this bug will be addressed?
Ok, so PR #6393 implies that you’ll have a default profile and some credentials set. That’s not the case, as AWS falls back to metadata API and the IAM role of the machine executing. I guess that’s the case with CodePipeline too (uses IAM attached to the job to set permissions).
I’ve released 1.48.3 which should address this issue
1.48.2 is broken too.
Still facing the same issue with 1.48.1, had to restore back to 1.48.0 in BuildSpec.yml.
Thank you, works on aws codebuild too
Excellent work. Really appreciate the dedication of maintainers. Thank you.
We are experiencing this issue on our Jenkins box as well which uses EC2 based IAM role permissions.
Serverless Error ---------------------------------------
ServerlessError: AWS provider credentials not found. Learn how to set up AWS provider credentials in our docs here: http://bit.ly/aws-creds-setup.
Get Support -------------------------------------------- Docs: docs.serverless.com Bugs: github.com/serverless/serverless/issues Issues: forum.serverless.com
Your Environment Information --------------------------- Operating System: linux Node Version: 10.16.0 Serverless Version: 1.48.2 Enterprise Plugin Version: 1.3.1 Platform SDK Version: 2.0.3
Had the same problem in codebuild stage in codepipeline. Serveless doesn’t seem to be able to get the role associated with the codebuild instance.
Went back to 1.48.0 and everything is working.