VM-Ware Image Import

Hi,

The VM Import/Export operations also requires service role with permissions on S3 and EC2, but also on KMS depending on the encryption. Could you check that it is configured correctly?

The VM image you're trying to import might have configurations that are incompatible with AWS VM Import/Export. For example, if you're importing a Windows VM, it might be failing to boot up, establish network connectivity, activate Windows using the Amazon EC2 Windows volume license, or meet other requirements. For Linux VMs, issues can arise if the VM has multi-boot volumes or multiple /etc directories, or if a logical volume on the virtual disk image fails to activate​.

AWS might not be able to access the S3 bucket where you uploaded the .ova file due to restrictions in the bucket policy or permissions. The bucket policy might not allow public read access, or the IAM policies might not provide the necessary permissions to access the bucket.

Since you mentioned that you've given S3FullAccess, it's likely that the issue might not be with the IAM policies. However, it's worth double-checking the S3 bucket policy and the permissions of the IAM role used for the VM import task. If the S3 bucket is not publicly accessible, ensure that the IAM role has the necessary permissions to access the bucket.

The VM you're importing might not be able to connect to the internet, which is a requirement for the import process. Check that your VM's networking settings allow outbound internet access.