mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #121] InvalidAccessKeyId Error while trying to connect to China Region #73
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#73
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 @zhouyuncsu on GitHub (Feb 12, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/121
Hello,
I clone the code 2015/2/12, and we currently aren't able to connect to the S3 buckets of the new region (China).
The command I typed is following:
s3fs -f prd-isidsh-foco-s3-01 mnt
The error message provided is following:
set_moutpoint_attribute(3482): PROC(uid=500, gid=500) - MountPoint(uid=500, gid=500, mode=40775)
s3fs_init(2669): init
s3fs_check_service(3022): check services.
CheckBucket(2526): check a bucket.
RequestPerform(1588): HTTP response code 403
RequestPerform(1607): HTTP response code 403 was returned, returning EPERM
CheckBucket(2578): Check bucket failed, S3 response:
InvalidAccessKeyIdThe AWS Access Key Id you provided does not exist in our records.4B5850D76A21EDF2WPnVNvZkM1MzbYQ4wsOct+IyTrC5CInwrrAZ2Xj8g5R1MWpAXVsXsT2INrQWVyH9I also have seen the issue bellow. But the error message is different, so I don't know is it the same problem.
https://github.com/s3fs-fuse/s3fs-fuse/issues/76
@ggtakec commented on GitHub (Mar 21, 2015):
Hi,
Could you try to use latest master branch codes?
It is merged for AWS signature v4 logic as deafult(please see #76), I think it probably works for China Region.
Thanks a lot.
@ggtakec commented on GitHub (Jan 17, 2016):
I'm closing this issue, if you have a problem yet, please post new issue or reopen this issue.
Thanks in advance for your help.