Skip to content

Conversation

@reweeden
Copy link
Contributor

@reweeden reweeden commented Oct 8, 2024

This eliminates the need for a workaround using a dummy group like this:

SOME_PATH: my-bucket

PRIVATE_BUCKETS:
  my-bucket:
    - NOACCESS
  my-bucket/prefix1/:
    - NOACCESS
    - group_1
  my-bucket/prefix2/:
    - NOACCESS
    - group_2

The new bucket configuration would look like this:

SOME_PATH: my-bucket

PRIVATE_BUCKETS:
  my-bucket/prefix1/:
    - group_1
  my-bucket/prefix2/:
    - group_2
NOACCESS_BUCKETS:
  my-bucket: Deny access to the empty prefix

I'm open to an alternative name to NOACCESS_BUCKETS.

This allows you to completely block access for some prefix which was 
previously impossible to do. This is useful for setting up an IAM 
compatible bucket with access for different prefixes, since the parent 
always needs to have equally or more restrictive permissions as the 
child prefixes. Setting the '' prefix to have no access, allows you to 
easily set whatever permission you want on any other prefix without 
causing IAM compatibility issues.
@reweeden reweeden changed the base branch from master to main April 7, 2025 15:51
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

Successfully merging this pull request may close these issues.

2 participants