Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow EC2 role credentials during function deployment
See original GitHub issueMy build server is an EC2 instance with a role that allows it to do everything it needs to perfrom deployments.
The dotnet lambda deploy-function command doesn’t understand this scenario. It assumes you either specify a credential profile or, if you don’t, it uses credentials from environment variables. It would be super nifty if it supported using role credentials as well.
It’s possible it already supports this and I’m doing something wrong. I tried removing the “profile” value from my aws-lambda-tools-defaults.json file and didn’t specify a profile on the command line. I wound up with this error message:
Error determining region for bucket dgi.deploy-lambda: Error determining region for bucket dgi.deploy-lambda: Access Denied
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Version 2.1.4 was just released with this fix to continuing looking for credentials when the profile can not be found.
I have made that change in the dev branch to go out with the next release https://github.com/aws/aws-extensions-for-dotnet-cli/commit/68e7329f587b18eb4ce6a7fd84c1b010eec83aa4