Import and export virtual machine images with Image Builder

1. Open the EC2 Image Builder console at https://console.aws.amazon.com/imagebuilder/.

2. Choose Images from the navigation pane.

3. Choose Import image.

4. Provide details for each of the following sections on the Import image page. Then choose Import image when you're done.

General

1. Specify a unique Name for the base image.

2. Specify a Version for the base image. Use the following format: major.minor.patch.

3. You can also enter an optional Description for the base image.

Base image operating system

1. Select the Image Operating System (OS) option that matches your VM OS platform.

2. Select the OS version that matches the version for your VM from the list.

VM import configuration

1. When you export your VM from its virtualization environment, that process creates a set of one or more disk container files. These act as snapshots of your VM’s environment, settings, and data. You can use these files to import your VM as the base image for your image recipe. For more information about importing VMs in Image Builder, see Import and export VM images.

   To specify the location of your import source, follow these steps:

    

   Import source

   Specify the source for the first VM image disk container or snapshot to import in the Disk container 1 section.

   1. Source – This can be either an S3 bucket, or an EBS snapshot.

   2. Select S3 location of disk – Enter the location in Amazon S3 where your disk images are stored. To browse for the location, choose Browse S3.

   3. To add a disk container, choose Add disk container.

    

2. IAM role

   To associate an IAM role with your VM import configuration, select the role from the IAM role dropdown list, or choose Create new role to create a new one. If you create a new role, the IAM Roles console page opens in a separate tab.

    

3. Advanced settings – optional

   The following settings are optional. With these settings, you can configure encryption, licensing, tags, and more for the base image that the import creates.

   Base image architecture

   To specify the architecture of your VM import source, select a value from the Architecture list.

   Encryption

   If your VM disk images are encrypted, you must provide a key to use for the import process. To specify a KMS key for the import, select a value from the Encryption (KMS key) list. The list contains KMS keys that your account has access to in the current Region.

   License management

   When you import a VM, the import process automatically detects the VM OS and applies the appropriate license to the base image. Depending on your OS platform, the license types are as follows:

   • License included – An appropriate AWS license for your platform is applied to your base image.

   • Bring your own license (BYOL) – Retains the license from your VM, if applicable.

   To attach license configurations created with AWS License Manager to your base image, select from the License configuration name list. For more information about License Manager, see Working with AWS License Manager

   Note

   • License configurations contain licensing rules based on the terms of your enterprise agreements.

   • Linux only supports BYOL licenses.

   Tags (base image)

   Tags use key-value pairs to assign searchable text to your Image Builder resource. To specify tags for the imported base image, enter key-value pairs using the Key and Value boxes.

   To add a tag, choose Add tag. To remove a tag, choose Remove tag.

1. Initiate a VM import, with the Amazon EC2 VM Import/Export import-image command in the AWS CLI. Make note of the task ID that is returned in the command response. You'll need it for the next step. For more information, see Importing a VM as an image using VM Import/Export in the VM Import/Export User Guide.

    

2. Create a CLI input JSON file

   To streamline the Image Builder import-vm-image command that is used in the AWS CLI, we create a JSON file that contains all of the import configuration that we want to pass into the command.

   Note

   The naming convention for the data values in the JSON file follows the pattern that is specified for the Image Builder API action request parameters. To review the API command request parameters, see the ImportVmImage command in the EC2 Image Builder API Reference.

   To provide the data values as command line parameters, refer to the parameter names specified in the AWS CLI Command Reference. to the Image Builder import-vm-image command as options.

   Here is a summary of the parameters that we specify in this example:

   • name (string, required) – The name for the Image Builder image resource to create as output from the import.

   • semanticVersion (string, required) – The semantic version for the output image that specifies the version in the following format, with numeric values in each position to indicate a specific version: <major>.<minor>.<patch>. For example, 1.0.0. To learn more about semantic versioning for Image Builder resources, see Semantic versioning in Image Builder.

   • description (string) – The description of the image recipe.

   • platform (string, required) – The operating system platform for the imported VM.

   • vmImportTaskId (string, required) – The ImportTaskId (AWS CLI) from the Amazon EC2 VM import process. Image Builder monitors the import process to pull in the AMI that it creates and build an Image Builder image resource that can be used in recipes right away.

   • clientToken (string, required) – A unique, case-sensitive identifier you provide to ensure idempotency of the request. For more information, see Ensuring idempotency in the Amazon EC2 API Reference.

   • tags (string map) – Tags are key-value pairs that are attached to the import resources. Up to 50 key-value pairs are allowed.

   Save the file as import-vm-image.json, to use in the Image Builder import-vm-image command.

   {
       "name": "example-request",
       "semanticVersion": "1.0.0",
       "description": "vm-import-test",
       "platform": "Linux",
       "vmImportTaskId": "import-ami-01ab234567890cd1e",
       "clientToken": "asz1231231234cs3z",
       "tags": {
       	"Usage": "VMIE"
       }
   }

3. Import the image

   Run the import-vm-image command, with the file that you created as input:

   aws imagebuilder import-vm-image --cli-input-json file://import-vm-image.json

   Note

   • You must include the file:// notation at the beginning of the JSON file path.

   • The path for the JSON file should follow the appropriate convention for the base operating system where you are running the command. For example, Windows uses the backslash (\) to refer to the directory path, while Linux and macOS use the forward slash (/).