Skip to content

Rework IAM documentation for directory buckets#1455

Open
c-hagem wants to merge 6 commits intoawslabs:mainfrom
c-hagem:doc-update/ami
Open

Rework IAM documentation for directory buckets#1455
c-hagem wants to merge 6 commits intoawslabs:mainfrom
c-hagem:doc-update/ami

Conversation

@c-hagem
Copy link
Contributor

@c-hagem c-hagem commented Jun 5, 2025

Reworks the section on IAM permissions to be more clearly split between general purpose buckets and directory buckets.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

Signed-off-by: Christian Hagemeier <[email protected]>
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 5, 2025 07:26 — with GitHub Actions Failure
@c-hagem c-hagem marked this pull request as ready for review June 5, 2025 07:33
@c-hagem c-hagem requested a review from dannycjones June 5, 2025 07:33
Copy link
Contributor

@muddyfish muddyfish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@c-hagem c-hagem changed the title Rework IAM for directory buckets Rework IAM documemtation for directory buckets Jun 6, 2025

Directory buckets, introduced with the S3 Express One Zone storage class, use a different authentication mechanism from general purpose buckets. Instead of using `s3:*` actions, you should allow the `s3express:CreateSession` action. Here is an example of least-privilege policy document.
### Directory buckets
Directory buckets, introduced with the S3 Express One Zone storage class, use a different authentication mechanism from general purpose buckets.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@c-hagem can you verify what type of auth Mountpoint (and CRT) tries to use when connecting to a local zone directory bucket? Does it try to create a session or use straight-forward IAM auth?

You don't need to be allowlisted to use the local zone, just know what a local zone access point looks like.


Directory buckets, introduced with the S3 Express One Zone storage class, use a different authentication mechanism from general purpose buckets. Instead of using `s3:*` actions, you should allow the `s3express:CreateSession` action. Here is an example of least-privilege policy document.
### Directory buckets
Directory buckets, introduced with the S3 Express One Zone storage class, use a different authentication mechanism from general purpose buckets.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should introduce XOZ in relation to the session-based auth, not directory buckets, since we now have Z-IA.

@dannycjones dannycjones changed the title Rework IAM documemtation for directory buckets Rework IAM documentation for directory buckets Jun 6, 2025
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
@c-hagem c-hagem had a problem deploying to PR integration tests June 6, 2025 13:26 — with GitHub Actions Failure
Co-authored-by: Daniel Carl Jones <[email protected]>
Signed-off-by: Christian Hagemeier <[email protected]>
@dannycjones dannycjones temporarily deployed to PR integration tests October 9, 2025 08:04 — with GitHub Actions Inactive
@dannycjones dannycjones requested a review from muddyfish October 9, 2025 08:45
@dannycjones dannycjones dismissed their stale review October 9, 2025 08:45

Taking over PR

Signed-off-by: Daniel Carl Jones <[email protected]>
@dannycjones dannycjones temporarily deployed to PR integration tests October 9, 2025 10:21 — with GitHub Actions Inactive
@dannycjones dannycjones self-assigned this Oct 9, 2025
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.

3 participants