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 when tried to create the bucket using Openstack v3 #581
Comments
What does |
PFB , content of bucketcreation script
If i use AWS CLI, I need to provide access key and secret key to access the s3 storage and currently, I don't have the same. Is there any other way to generate the access and secret key with s3proxy? So that I can use them with the AWS CLI utility. |
I am having auth issues when using the local filesystem, so no underlying issues regarding auth. When set to aws-v2-or-v4 and identity and credential are set, presigned urls work as well as non-presigned urls. Meaning no auth required to access even though identity and credentials are set. When set to aws-v4 and identity and credential are set any presigned urls fail with 403 forbidden while non-presigned/non authorized can download files. This is exactly opposite of the point of authorization. When set to aws-v2 it is the same as aws-v2-or-v4. Anonymous access as well as Authorized access are allowed. Any idea @gaul ? I have been tinkering with it for awhile and even build a new executable from the git about 20 minutes ago. Still no dice. This is on ubuntu 20 by the way. My current solution using rclone deals with the exact same problem as they use GofakeS3. |
Hi
I am using the OpenStack Keystone v3 sample to connect to OpenStack Swift storage to create the buckets and objects. I have used the s3proxy and configured the properties file to start the server and the connection was successful. However, due to some reasons, I am unable to create the bucket and objects. Could you please let me know what could be the reason?
This is the error i am getting while creating the bucket:
PFB properties file:
The text was updated successfully, but these errors were encountered: