ClientError: ENA must be supported with uefi boot-mode


I am trying to run a Windows 10 Home VM in EC2. The plan is to run it in EC2 for about two days, our partner will access it through RDP and then transfer it back to VirtualBox. I prepared the image in VirtualBox, then exported .ova file, uploaded it to S3 and tried to convert it to AMI with following command as described here.

$ aws ec2 import-image --description "Windows 10 VM" --platform Windows --disk-containers "file://foo/containers.json" --boot-mode uefi --license-type BYOL --architecture x86_64

But I get following error after the import process reaches progress 27%:

$ aws ec2 describe-import-image-tasks --import-task-ids fooID
    "ImportImageTasks": [
            "Architecture": "x86_64",
            "Description": "Windows 10 VM",
            "ImportTaskId": "fooID",
            "LicenseType": "BYOL",
            "Platform": "Windows",
            "SnapshotDetails": [
                    "DeviceName": "/dev/sda1",
                    "DiskImageSize": 8298251264.0,
                    "Format": "VMDK",
                    "Status": "completed",
                    "Url": "s3://foo/Windows-10.ova",
                    "UserBucket": {
                        "S3Bucket": "foo",
                        "S3Key": "Windows-10.ova"
            "Status": "deleted",
            "StatusMessage": "ClientError: ENA must be supported with uefi boot-mode",
            "Tags": [],
            "BootMode": "uefi"

I have done these steps:

  1. Installed ENA driver (Didn't help)
  2. Installed AWS CLI (Didn't help)

What should I do? I know for sure that the VM boots using UEFI in VBox. Should I convert it to BIOS boot? Is there anything I need to install or what? Google returns only this thread which is unanswered and they are talking about instance types. So I asked my own question.

  • As expected - the AWS CLI installation didn't help. So what next? I've edited the question.

1 Answer
Accepted Answer

As per the docs here, it's not currently supported I'm afraid -

Currently, we do not support importing Windows with UEFI Secure Boot by using the import-image command.

If you change the boot mode to legacy BIOS prior to importing this should work.

answered 2 years ago
  • That's dissabpointing. I'll try GCloud before converting it to BIOS.

    EDIT: GCloud is even worse. AWS gives you consistent error while Google fails with 4 different error messages which don't make sense...

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions