Closed ltricard closed 10 months ago
@thomasmichaelwallace Is it possible to have the plugin fall back to unmodified behaviour if the .aws/credentials
file is missing? This bug with IAM roles makes it hard to use the plugin since it breaks in CI.
I agree this could be useful behaviour- although it could be harder than you expect to implement because of the way credentials get resolved natively by serverless is still different from the way the aws-sdk works.
For what it's worth, I think this should just work if you have the AWS_ACCESS_KEY
&c. variables set in your ci/cd environment.
In general, however, I would recommend moving away from AWS managed profiles and instead using something like https://github.com/99designs/aws-vault.
I don't have time to work on this plugin any more - I moved to the AWS-CDK and haven't really looked back.
But I accept PRs 😄
It's a bit late, but I've added a bit to the readme about how to deal with this CI/CD scenario by creating a temporary ~/.aws/credentials
file- see:
I'll close this issue for now, but feel free to re-open if you have any trouble.
Describe the bug when we use plugin on EC2 with IAM role, it doesn't work anymore
To Reproduce Steps to reproduce the behavior:
Expected behavior get credentials from IAM Role
Screenshots
Additional infos:
I try to add ~/.aws/config with only
And try again
Desktop (please complete the following information):
Additional context When we comment the plugin, it works fine. Does it possible to have a (env?) variable to by-pass SSO authentication ? Otherwise with SSO, this plugin is great :)