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

Add IAM Role support for the AWS S3 fileserver #2026

Open
2 of 6 tasks
lumattr opened this issue Mar 18, 2024 · 0 comments
Open
2 of 6 tasks

Add IAM Role support for the AWS S3 fileserver #2026

lumattr opened this issue Mar 18, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned

Comments

@lumattr
Copy link

lumattr commented Mar 18, 2024

Additional context
The S3 fileserver support has parameters here but the appear to use an access key and secret key parameter which goes against AWS best practice guidelines.

This function appears to use the parameters but would need to be updated to expect the environment vars for the different metadata contexts available in AWS, EKS, EC2 etc.

Is your feature request related to a problem? Please describe.
I would like to use the S3 filestore but i am unable to create an access key and secret from from an IAM user.

Describe the solution you'd like
I would like to be able to just add additional IAM polices to the service account configured by the Helm chart, that is used by the services in the console, that would provide the acces to the specified bucket.

Components/Services

  • UI/Frontend
  • API/Backend
  • Agent
  • Deployment/YAMLs
  • CI/CD Integration
  • Other (specify)
@lumattr lumattr added enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned labels Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned
Projects
None yet
Development

No branches or pull requests

2 participants