You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: