mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #88] Support For Different AWS Signature Versions #52
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FergusRedican on GitHub (Nov 24, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/88
Hi, This is not an issue per say but I wanted to ask a question for clarification and did not know where to:)
I wanted to know if there are any restrictions for using s3fs-fuse based on different signature versions available within AWS. Some regions support Sig V4 for example, others can support Sig V2 &/Or Sig V4. Maybe this is not relevant but I have come across issues before with client apps for S3 buckets and wondered if there could be similar restrictions with s3fs-fuse.
Thanks for any help with this!
@gaul commented on GitHub (Nov 24, 2014):
@FergusRedican s3fs only supports V2 signatures presently. We will add support for V4 signatures in #76 to allow use of Frankfurt region and any future regions.
@FergusRedican commented on GitHub (Nov 26, 2014):
Hi Andrew. Thank you for this feedback.