-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access Denied Error: Check bucket failed with full S3 Access #1452
Comments
Apparently, you need to wait a few hours so amazon can update the permissions across their system. |
Did you have to do anything else aside from waiting? I am experiencing the exact same issue but it's been the case for at least a day now @valerius21 |
A few things could be going on with the original issue -- creating a bucket in one region and recreating it in another might make the DNS entries temporarily stale. Specifying the full URL suck as https://s3.us-west-1.amazonaws.com and the endpoint such as us-west-1 should always work though. |
I tried with both |
Confirm I am experiencing the same behaviour. Both with the -o Endpoint and -o Url parameters configured. I am able to connect to buckets that were created prior to the test bucket I am working with. There is clearly an issue in passing the endpoint/url inside s3fs. When interacting with newly created buckets using the AWS-CLI / PowerShell / Terraform, passing the region is sufficient. The requirement for passing the region is because of DNS propagation not IAM policy permissions. Please re-open and investigate? |
Additional Information
Version of s3fs being used (s3fs --version)
1.86
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.9-3
Kernel information (uname -r)
5.4.0-48-generic
GNU/Linux Distribution, if applicable (cat /etc/os-release)
s3fs command line used, if applicable
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages
Details about the issue
Using the
~/.aws/credentials
file over the~/.passwd-s3fs
file produces the same error. The IAM role has full S3 access and the permissions have been tested with the same profile on the aws cli.No files show up in the desired folder.
I am getting the following error when trying to mount the s3 bucket to a folder in my home directory:
The text was updated successfully, but these errors were encountered: