Add support for S3 Express One Zone [tracking]

[rcoh]

Describe the feature

Add Rust SDK support for S3 Express One Zone

Use Case

Enable the Rust SDK to use One Zone buckets

Proposed Solution

We have internally agreed-upon design to follow.

Work breakdown

• (smithy-rs#3386) Add placeholder types and enable control flow to be redirected for S3 Express use case
• (smithy-rs#3388) Use create_session S3 API to obtain a session token for S3 Express
• (smithy-rs#3388) Implement the signer for S3 Express (presigning & header signing)
• (smithy-rs#3393) Modify S3 Express default for checksum
• (smithy-rs#3390) Implement S3 Express identity cache
• (smithy-rs#3433) Implement DisableS3ExpressSessionAuth (some part of the implementation is not supported until Support service specific configs appearing in the general section of a profile file #1073 is addressed)
• (smithy-rs#3462) Add various API tests in canary
• (optional for initial release) - (smithy-rs#3446) Add benchmark to profile S3 Express use cases

A note for the community

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue, please leave a comment

[HammadB]

I noticed this was marked as p1, is this actively being worked on / is their a timeline? Debating rolling my own

[shikhar]

@HammadB in case it helps, I found directory buckets to be usable with disable_s3_express_session_auth(true), so I'm holding off for official support. I am seeing sub-20 ms rather than the promised sub-10 ms latencies though, which I am hopeful will improve with session-based auth.

[rcoh]

I noticed this was marked as p1, is this actively being worked on / is their a timeline? Debating rolling my own
Yes this is in progress.

[jdisanti]

This went out in yesterday's release.

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.