The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Anatoly (staff), Max (staff)
Hi. I'm logged in as root. I've created a new bucket with ACLs disabled and public access disabled. I've created a new access key. Same problem.yaroslav (staff) wrote:The issue is on the AWS side as the application cannot make the changes using the credentials you supplied.
Try the following:
1. Make sure you are logged as root.
2. Create a bucket and the access key for it.
3. Try conversion over again.
This can be the key.ACLs disabled and public access disabled.
Are you saying to make sure that ACL's are disabled and public access is also disabled in this new account?yaroslav (staff) wrote:Hi,This can be the key.ACLs disabled and public access disabled.
I ran the conversion with my personal AWS account without a hitch.
Can you please try creating a new AWS account to double-check that?
If it's working in your account, would you mind sharing all of the settings with me?yaroslav (staff) wrote:Sorry for misleading you. I read a bit more about this issue. Any new account should have ACLs (https://docs.aws.amazon.com/AmazonS3/la ... rview.html) and public access (https://docs.aws.amazon.com/AmazonS3/la ... ucket.html) disabled by default.
The error you faced seems to be a result of recent changes in AWS.
What I found (recent thread) is https://stackoverflow.com/questions/760 ... enforced-s.
More detail https://docs.aws.amazon.com/AmazonS3/la ... rship.html and https://stackoverflow.com/questions/760 ... ror-for-my.
What I am trying to say is that something got changed on the AWS side recently. I will log a call with R&D to see if it can be worked around on our side.
OK support case has been logged.yaroslav (staff) wrote:Please log a call with us at support@starwind.com.
Use link to this thread and 972402 as your references.
Just wanted to mention that the issue is on the AWS side, we will need time to implement and test the workaround on our side.