Skip to content
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

S3 on AWS shouldn't require Access Key and Secret Key #2

Open
dusty73 opened this issue Mar 3, 2021 · 0 comments
Open

S3 on AWS shouldn't require Access Key and Secret Key #2

dusty73 opened this issue Mar 3, 2021 · 0 comments

Comments

@dusty73
Copy link

dusty73 commented Mar 3, 2021

Using this plugin on a server installed on EC2 instance I noticed that it is not possible to use the IAM Role attached to the instance in order to grant the rights needed to access the S3 bucket and is always mandatory Access Key and Secret Key.

This is a bit of an anti-pattern for AWS, that recommend to use IAM Role to grant permissions whenever it's possible and use static credentials as a last resort.

Looking at the code I see that instead of the AWS SDK it's been used the Minio Clienti library. Minio and any other object store compliant with the S3 standard can interact with the standard AWS SDK. Using it you would have the ability to use automatically the Role attached to the EC2 instance and alternatively to continue to supply access key and secret key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant