-
Notifications
You must be signed in to change notification settings - Fork 402
Open
Description
The current IGV S3 integration has two issues when using Amazon → Load from S3 bucket:
- Permission Requirements: Requires
s3:ListAllMyBucketsIAM permission, which many enterprise environments cannot grant due to security policies requiring least-privilege access - Performance Issues: When AWS accounts have 500+ buckets, listing and navigating the bucket selection UI becomes slow and cumbersome
Proposed Solution
Add support for an environment variable (e.g., IGV_S3_BUCKETS) that allows users to specify a list of allowed S3 buckets:
export IGV_S3_BUCKETS="bucket1,bucket2,bucket3"
Behavior:
- If the environment variable is set: Display only the specified buckets (no
s3:ListAllMyBucketscall required) - If not set: Use current behavior (list all accessible buckets)
Benefits
- Eliminates need for
s3:ListAllMyBucketspermission - Improves performance by avoiding API calls and reducing UI clutter
- Better user experience showing only relevant buckets
- Fully backward compatible with existing deployments
Use Case
Enterprise deployments where:
- IAM roles have access to specific buckets only
- Security policies prohibit broad listing permissions
- AWS accounts contain hundreds of buckets across multiple teams
Can this be taken up as a feature request? We would like to contribute to this fearure if there's interest.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels