Error V2Ving from Aws to Hyper-V

VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

logeswaran.t
Posts: 1
Joined: Sat Sep 14, 2024 4:00 am

Sat Sep 14, 2024 4:03 am

Hi Team,

Today i have tried to migrate the windows VM from AWS to my local environment. I have received the same error message in the log.

9/14 9:12:47.315 e3c Facility ???INFO: WrapperS3::initS3Client: Created S3 client in ap-south-2 region
9/14 9:12:47.315 e3c Facility ???INFO: AWSDisk::CreateInputImage: Create bucket name - v2v-converter-bucket-c1460ae2-a84d-463b-ad67-3eef5581b6e
9/14 9:12:48.894 e3c Facility ???INFO: WrapperAWS::detachVolumesOnly: instanceId - i-0a6843e9649184472
9/14 9:12:49.347 e3c Facility ???ERROR: WrapperAWS::createInstanceExportTask: CreateInstanceExportTask is fail - Unable to parse ExceptionName: AuthFailure Message: Bucket must be owned by the same S3 account and READ_ACL and WRITE permissions are required on the destination bucket. Please refer to the API documentation for details.
9/14 9:12:49.347 e3c Facility ???ERROR: VMConverter::AWSConverter::InstanceExport: createInstanceExportTask - Unable to parse ExceptionName: AuthFailure Message: Bucket must be owned by the same S3 account and READ_ACL and WRITE permissions are required on the destination bucket. Please refer to the API documentation for details.
9/14 9:12:49.347 e3c Facility ???INFO: WrapperAWS::attachVolumes: instanceId - i-0a6843e9649184472
9/14 9:12:49.347 e3c Facility ???ERROR: AWSDisk::CreateInputImage: Error InstanceExport - Unable to parse ExceptionName: AuthFailure Message: Bucket must be owned by the same S3 account and READ_ACL and WRITE permissions are required on the destination bucket. Please refer to the API documentation for details.
9/14 9:12:49.347 e3c Facility ???INFO: CPPConverting::ConvertDisks: CreateInputImage: 1
9/14 9:12:49.738 e3c Facility ???ERROR: CPPConverting::Convert: FAILED

Any Ideas on this ?
yaroslav (staff)
Staff
Posts: 3424
Joined: Mon Nov 18, 2019 11:11 am

Sat Sep 14, 2024 10:36 am

The log points to the authentication issues with your AWS account.
Please try with the root user.
Post Reply