Error V2Ving from Aws to Hyper-V

[Mlewis]

Followed the Starwind guide for Aws migration out and in to HyperV but getting the following errors:

Error creating bucket.
Error opening image.
Unable to parse exception name InvalidAdBucketWidthObjectOwnership...

With the last error like being the clue.

Any ideas?

[yaroslav (staff)]

Hi,

Please review the privileges AWS account has. The issue is related to insufficient privileges.

[Mlewis]

That's what I thought as well but I followed the article in the help file:

https://www.starwindsoftware.com/v2v-he ... vices.html

But I am still getting this error.

What should I check specifically? I created the Access Keys from the AWS root user, opened the ports in the security group that's associated with the instance, and I created a key pair. Not sure what else to do.

[yaroslav (staff)]

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.

[Mlewis]

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.

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.

I've also tried this on a totally different AWS organization using that orgs root account with same results.

There has to be some prerequisite that's not mentioned in the Starwind documentation that's not being met. Would you please double check with your team on this?

Thank you for the assistance. Greatly appreciated.

[yaroslav (staff)]

Hi,

ACLs disabled and public access disabled.

This can be the key.
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?

[Mlewis]

Hi,

ACLs disabled and public access disabled.

This can be the key.
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?

Are you saying to make sure that ACL's are disabled and public access is also disabled in this new account?

[yaroslav (staff)]

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.

[Mlewis]

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.

If it's working in your account, would you mind sharing all of the settings with me?

[Mlewis]

Just bumping this, really need to get this working.

[yaroslav (staff)]

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.

[Mlewis]

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.

OK support case has been logged.

I'm available at your convenience to troubleshoot this.

Thanks

[yaroslav (staff)]

R&D is working on the workaround. I will keep you posted in the support case.