Tutorial: Copying an OMI

The goal of this tutorial is to copy an OUTSCALE Machine Image (OMI) between accounts within one Region or across different Regions.

Copying an OMI Within One Region

  1. Grant the appropriate permissions for your OMI to the account you want to share the OMI with. For more information, see Modifying the Attributes of an OMI.

  2. The other account must copy the OMI to their account. For more information, see Copying an OMI Within One Region.
    The OMI is copied to the account of the other account. This copy is independent from the source OMI and has its own ID.

Copying an OMI Across Regions

Before you begin: Create an OUTSCALE Storage Object (OOS) bucket in the same Region as the source OMI. For more information, see Creating a Bucket.

Before exporting an OMI or a snapshot to another Region, you need to make sure that this action is authorized by all applicable third-party licenses. If the export is authorized, only an OMI export guarantees the application of third-party licenses in the target Region, whereas a snapshot export does not.

You cannot copy a shared or public OMI to a different Region, as it does not belong to you. To do so, you must first copy it to your account in the same Region. The copy of the OMI then belongs to you and is independent from the source one. For more information, see Copying an OMI Within One Region.

Export the OMI to an OOS bucket

  1. If you are using Cockpit, export the OMI to the OOS bucket. For more information, see Exporting an OMI to a Bucket.

  2. If you are using the API, do the following actions:

    1. Create a manifest file for the OMI export task. For more information, see Creating a Manifest File for an Image Export Task.

    2. Upload the manifest file to the OOS bucket. For more information, see Uploading an Object to a Bucket.

    3. Create a pre-signed URL for the manifest file. For more information, see Configuring a Pre-Signed URL.

Import the OMI From an OOS Bucket

  1. If you are using the APIs, send the pre-signed URL of the manifest file to the other account.

  2. The other account imports the OMI to their account. For more information, see Importing an OMI from a Bucket.
    The OMI is copied to the account of the other account. This copy is independent from the source OMI and has its own ID.

Related Pages