Copying an OMI Across Regions
You can copy an OUTSCALE Machine Image (OMI) between accounts located in different Regions, using an export/import method.
This enables you to launch similar instances in different Regions, and to improve the availability of your applications in different Regions.
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.
To copy an OMI within a single Region, you can either use this same export/import method or use the
copy-image direct method. For more information, see Copying an OMI Within One Region.
Before you begin: The owner of the source OMI first needs to export it to an OUTSCALE Object Storage (OOS) bucket. The other user then needs to import it in their account using the pre-signed URL of the manifest file of the OMI in the OOS bucket.
The owner of the source OMI exports it to an OOS bucket. For more information, see Exporting an OMI to a Bucket.
The owner of the source OMI provides the other user with one of the following elements:
A pre-signed URL to the manifest file. For more information, see Configuring a Pre-signed URL.
The path to the OMI in the OOS bucket, if the other user’s account is in the same Region.
This account must have the permissions to access this OMI. For more information, see Configuring an Object ACL.
The manifest file is obsolete seven days after a completed export as it contains pre-signed URLs to the appropriate snapshots (pre-signed URL are valid for only seven days).
The other user imports the OMI from the OOS bucket. For more information, see Importing an OMI from a Bucket.
A copy of the OMI is created in the user’s account.
Corresponding API Methods