Skip to content

doc/dev/radosgw: draft design for s3express CreateSession - #71066

Draft
cbodley wants to merge 1 commit into
ceph:mainfrom
cbodley:wip-79514
Draft

doc/dev/radosgw: draft design for s3express CreateSession#71066
cbodley wants to merge 1 commit into
ceph:mainfrom
cbodley:wip-79514

Conversation

@cbodley

@cbodley cbodley commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

a draft design for https://tracker.ceph.com/issues/79514, exploring the use of aws' s3express:CreateSession api

Show available Jenkins commands

You must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.

Signed-off-by: Casey Bodley <cbodley@redhat.com>

## evaluation

are there potential performance improvements here? i think the idea is that, by doing authorization up front during CreateSession, subsequent requests could avoid the overhead of reading/evaluating iam policies. this _might_ mean the requests could avoid reading/decoding the user/account metadata at all. however, we do expect the metadata cache to hide a lot of this overhead

@cbodley cbodley Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

an important part of sigv4 is looking up the user by its access key to learn the corresponding secret key, so i don't think we could eliminate that read entirely

edit: oops, these subsequent requests would be using the temporary access/secret keys generated by CreateSession. these temporary credentials could just be encoded in the session token like we do for sts

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.

1 participant