Copier une OMI dans la même Région

Vous pouvez copier une image machine OUTSCALE (OMI) dans la même Région que votre compte.

L’OMI source peut soit appartenir à votre compte, soit être une OMI partagée appartenant à un autre compte.

La copie de l’OMI appartient à votre compte, est indépendante de l’OMI source et a son propre ID. Tout snapshot utilisé par l’OMI source est également copié dans votre compte.

Pour copier une OMI située dans une Région différente de celle de votre compte, voir Copier une OMI vers d’autres Régions.

Copier une image dans une même Région avec Cockpit v2

Avant de commencer : Si l’image que vous voulez copier ne vous appartient pas, son propriétaire doit la partager avec vous. Pour en savoir plus, voir Modifier les attributs d’une OMI.

Dans le dashboard Images, cochez la case de l’image que vous voulez copier.
L’image est sélectionnée.
Cliquez sur Copier.
La boîte de dialogue COPIER UNE IMAGE apparaît.
Dans le champ Nom, tapez un nom pour la copie de l’image.

Ce nom doit être unique et doit contenir entre 3 et 128 caractères. Les caractères autorisés sont a-z, A-Z, 0-9, l’espace et [_()/.-].
(optionnel) Dans le champ Description, tapez une description pour la copie de l’image.
Cliquez sur Copier.
L’image est copiée dans votre compte.

Copier une OMI dans une même Région avec OSC CLI

Avant de commencer : Si l’OMI que vous voulez copier ne vous appartient pas, son propriétaire doit la partager avec vous. Pour en savoir plus, voir Modifier les attributs d’une OMI.

À ce jour, cette section est disponible en anglais uniquement.

The CreateImage command creates an OUTSCALE machine image (OMI).
You can use this method for different use cases:

Creating from a VM: You create an OMI from one of your virtual machines (VMs).
Copying an OMI: You copy an existing OMI. The source OMI can be one of your own OMIs, or an OMI owned by another account that has granted you permission via the UpdateImage method.
Registering from a snapshot: You register an OMI from an existing snapshot. The source snapshot can be one of your own snapshots, or a snapshot owned by another account that has granted you permission via the UpdateSnapshot method.
Registering from a bucket by using a manifest file: You register an OMI from the manifest file of an OMI that was exported to an OUTSCALE Object Storage (OOS) bucket. First, the owner of the source OMI must export it to the bucket by using the CreateImageExportTask method. Then, they must grant you permission to read the manifest file via a pre-signed URL. For more information, see Creating a Pre-Signed URL.

Registering from a bucket enables you to copy an OMI across Regions.

For more information, see About OMIs.

Request sample: Copying an OMI

$ osc-cli api CreateImage --profile "default" \
    --ImageName "copy-image-example" \
    --SourceImageId "ami-12345678" \
    --SourceRegionName "eu-west-2"

This command contains the following attributes that you need to specify:

Description: (optional) A description for the new OMI.
DryRun: (optional) If true, checks whether you have the required permissions to perform the action.
ImageName: (optional) A unique name for the new OMI.
Constraints: 3-128 alphanumeric characters, underscores (_), spaces ( ), parentheses (()), slashes (/), periods (.), or dashes (-).
ProductCodes: (optional) The product codes associated with the OMI.
SourceImageId: (optional) (required) When copying an OMI: The ID of the OMI you want to copy.
SourceRegionName: (optional) (required) When copying an OMI: The name of the source Region (always the same as the Region of your account).

The CreateImage command returns the following elements:

Image: Information about the OMI.
- AccountAlias: The account alias of the owner of the OMI.
- AccountId: The account ID of the owner of the OMI.
- Architecture: The architecture of the OMI.
- BlockDeviceMappings: One or more block device mappings.
  - Bsu: Information about the BSU volume to create.
    
    DeleteOnVmDeletion: By default or if set to true, the volume is deleted when terminating the VM. If false, the volume is not deleted when terminating the VM.
    
    Iops: The number of I/O operations per second (IOPS). This parameter must be specified only if you create an io1 volume. The maximum number of IOPS allowed for io1 volumes is 13000 with a maximum performance ratio of 300 IOPS per gibibyte.
    
    SnapshotId: The ID of the snapshot used to create the volume.
    
    VolumeSize: The size of the volume, in gibibytes (GiB).
    If you specify a snapshot ID, the volume size must be at least equal to the snapshot size.
    If you specify a snapshot ID but no volume size, the volume is created with a size similar to the snapshot one.
    
    VolumeType: The type of the volume (standard | io1 | gp2). If not specified in the request, a standard volume is created.
    For more information about volume types, see About Volumes > Volume Types and IOPS.
  - DeviceName: The device name for the volume. For a root device, you must use /dev/sda1. For other volumes, you must use /dev/sdX, /dev/sdXX, /dev/xvdX, or /dev/xvdXX (where the first X is a letter between b and z, and the second X is a letter between a and z).
  - VirtualDeviceName: The name of the virtual device (ephemeralN).
- CreationDate: The date and time (UTC) at which the OMI was created.
- Description: The description of the OMI.
- FileLocation: The location from which the OMI files were created.
- ImageId: The ID of the OMI.
- ImageName: The name of the OMI.
- ImageType: The type of the OMI.
- PermissionsToLaunch: Permissions for the resource.
  - AccountIds: One or more account IDs that the permission is associated with.
  - GlobalPermission: A global permission for all accounts.
    (Request) Set this parameter to true to make the resource public (if the parent parameter is Additions) or to make the resource private (if the parent parameter is Removals).
    (Response) If true, the resource is public. If false, the resource is private.
- ProductCodes: The product codes associated with the OMI.
- RootDeviceName: The name of the root device.
- RootDeviceType: The type of root device used by the OMI (always bsu).
- State: The state of the OMI (pending | available | failed).
- StateComment: Information about the change of state.
  - StateCode: The code of the change of state.
  - StateMessage: A message explaining the change of state.
- Tags: One or more tags associated with the OMI.
  - Key: The key of the tag, with a minimum of 1 character.
  - Value: The value of the tag, between 0 and 255 characters.
ResponseContext: Information about the context of the response.
- RequestId: The ID of the request.

Result sample: Copying an OMI

{
  "ResponseContext": {
    "RequestId": "0475ca1e-d0c5-441d-712a-da55a4175157"
  },
  "Image": {
    "StateComment": {},
    "State": "available",
    "RootDeviceType": "bsu",
    "RootDeviceName": "/dev/sda1",
    "ProductCodes": [
      "0001"
    ],
    "PermissionsToLaunch": {
      "GlobalPermission": false,
      "AccountIds": []
    },
    "AccountId": "123456789012",
    "Tags": [],
    "Description": "",
    "ImageId": "ami-12345678",
    "BlockDeviceMappings": [
      {
        "DeviceName": "/dev/sda1",
        "Bsu": {
          "VolumeType": "standard",
          "DeleteOnVmDeletion": true,
          "VolumeSize": 50,
          "SnapshotId": "snap-12345678"
        }
      }
    ],
    "ImageType": "machine",
    "CreationDate": "2010-10-01T12:34:56.789Z",
    "FileLocation": "123456789012/copy-image-example",
    "Architecture": "x86_64",
    "ImageName": "copy-image-example"
  }
}

Copier une OMI dans une même Région avec oapi-cli

Avant de commencer : Si l’OMI que vous voulez copier ne vous appartient pas, son propriétaire doit la partager avec vous. Pour en savoir plus, voir Modifier les attributs d’une OMI.

À ce jour, cette section est disponible en anglais uniquement.

The CreateImage command creates an OUTSCALE machine image (OMI).
You can use this method for different use cases:

Creating from a VM: You create an OMI from one of your virtual machines (VMs).
Copying an OMI: You copy an existing OMI. The source OMI can be one of your own OMIs, or an OMI owned by another account that has granted you permission via the UpdateImage method.
Registering from a snapshot: You register an OMI from an existing snapshot. The source snapshot can be one of your own snapshots, or a snapshot owned by another account that has granted you permission via the UpdateSnapshot method.
Registering from a bucket by using a manifest file: You register an OMI from the manifest file of an OMI that was exported to an OUTSCALE Object Storage (OOS) bucket. First, the owner of the source OMI must export it to the bucket by using the CreateImageExportTask method. Then, they must grant you permission to read the manifest file via a pre-signed URL. For more information, see Creating a Pre-Signed URL.

Registering from a bucket enables you to copy an OMI across Regions.

For more information, see About OMIs.

Request sample: Copying an OMI

$ oapi-cli --profile "default" CreateImage \
    --ImageName "copy-image-example" \
    --SourceImageId "ami-12345678" \
    --SourceRegionName "eu-west-2"

This command contains the following attributes that you need to specify:

Description: (optional) A description for the new OMI.
DryRun: (optional) If true, checks whether you have the required permissions to perform the action.
ImageName: (optional) A unique name for the new OMI.
Constraints: 3-128 alphanumeric characters, underscores (_), spaces ( ), parentheses (()), slashes (/), periods (.), or dashes (-).
ProductCodes: (optional) The product codes associated with the OMI.
SourceImageId: (optional) (required) When copying an OMI: The ID of the OMI you want to copy.
SourceRegionName: (optional) (required) When copying an OMI: The name of the source Region (always the same as the Region of your account).

The CreateImage command returns the following elements:

Image: Information about the OMI.
- AccountAlias: The account alias of the owner of the OMI.
- AccountId: The account ID of the owner of the OMI.
- Architecture: The architecture of the OMI.
- BlockDeviceMappings: One or more block device mappings.
  - Bsu: Information about the BSU volume to create.
    
    DeleteOnVmDeletion: By default or if set to true, the volume is deleted when terminating the VM. If false, the volume is not deleted when terminating the VM.
    
    Iops: The number of I/O operations per second (IOPS). This parameter must be specified only if you create an io1 volume. The maximum number of IOPS allowed for io1 volumes is 13000 with a maximum performance ratio of 300 IOPS per gibibyte.
    
    SnapshotId: The ID of the snapshot used to create the volume.
    
    VolumeSize: The size of the volume, in gibibytes (GiB).
    If you specify a snapshot ID, the volume size must be at least equal to the snapshot size.
    If you specify a snapshot ID but no volume size, the volume is created with a size similar to the snapshot one.
    
    VolumeType: The type of the volume (standard | io1 | gp2). If not specified in the request, a standard volume is created.
    For more information about volume types, see About Volumes > Volume Types and IOPS.
  - DeviceName: The device name for the volume. For a root device, you must use /dev/sda1. For other volumes, you must use /dev/sdX, /dev/sdXX, /dev/xvdX, or /dev/xvdXX (where the first X is a letter between b and z, and the second X is a letter between a and z).
  - VirtualDeviceName: The name of the virtual device (ephemeralN).
- CreationDate: The date and time (UTC) at which the OMI was created.
- Description: The description of the OMI.
- FileLocation: The location from which the OMI files were created.
- ImageId: The ID of the OMI.
- ImageName: The name of the OMI.
- ImageType: The type of the OMI.
- PermissionsToLaunch: Permissions for the resource.
  - AccountIds: One or more account IDs that the permission is associated with.
  - GlobalPermission: A global permission for all accounts.
    (Request) Set this parameter to true to make the resource public (if the parent parameter is Additions) or to make the resource private (if the parent parameter is Removals).
    (Response) If true, the resource is public. If false, the resource is private.
- ProductCodes: The product codes associated with the OMI.
- RootDeviceName: The name of the root device.
- RootDeviceType: The type of root device used by the OMI (always bsu).
- State: The state of the OMI (pending | available | failed).
- StateComment: Information about the change of state.
  - StateCode: The code of the change of state.
  - StateMessage: A message explaining the change of state.
- Tags: One or more tags associated with the OMI.
  - Key: The key of the tag, with a minimum of 1 character.
  - Value: The value of the tag, between 0 and 255 characters.
ResponseContext: Information about the context of the response.
- RequestId: The ID of the request.

Result sample: Copying an OMI

{
  "ResponseContext": {
    "RequestId": "0475ca1e-d0c5-441d-712a-da55a4175157"
  },
  "Image": {
    "StateComment": {},
    "State": "available",
    "RootDeviceType": "bsu",
    "RootDeviceName": "/dev/sda1",
    "ProductCodes": [
      "0001"
    ],
    "PermissionsToLaunch": {
      "GlobalPermission": false,
      "AccountIds": []
    },
    "AccountId": "123456789012",
    "Tags": [],
    "Description": "",
    "ImageId": "ami-12345678",
    "BlockDeviceMappings": [
      {
        "DeviceName": "/dev/sda1",
        "Bsu": {
          "VolumeType": "standard",
          "DeleteOnVmDeletion": true,
          "VolumeSize": 50,
          "SnapshotId": "snap-12345678"
        }
      }
    ],
    "ImageType": "machine",
    "CreationDate": "2010-10-01T12:34:56.789Z",
    "FileLocation": "123456789012/copy-image-example",
    "Architecture": "x86_64",
    "ImageName": "copy-image-example"
  }
}

Copier une OMI dans une même Région avec AWS CLI

Avant de commencer :

Installez et configurez AWS CLI. Pour en savoir plus, voir Installer et configurer AWS CLI.
Assurez-vous d’avoir les permissions pour l’OMI : si l’OMI que vous voulez copier ne vous appartient pas, son propriétaire doit la partager avec vous. Pour en savoir plus, voir Modifier les attributs d’une OMI.

Pour copier une OMI dans votre compte, utilisez la commande copy-image en suivant cette syntaxe :

Requête

$ aws ec2 copy-image \
    --profile YOUR_PROFILE \
    --source-region eu-west-2 \
    --source-image-id ami-12345678 \
    --name OMI_name \
    --description Description of the OMI \
    --endpoint https://fcu.eu-west-2.outscale.com

Cette commande contient les attributs suivants que vous devez spécifier :

(optionnel) profile : Le profil nommé que vous voulez utiliser, créé pendant la configuration d’AWS CLI. Pour en savoir plus, voir Installer et configurer AWS CLI.
source-region : Le nom de la Région source, qui doit être la même que la Région de votre compte.
source-image-id : L’ID de l’OMI que vous voulez copier.

name : Le nom de la copie de l’OMI.

Ce nom doit être unique et peut contenir n’importe quel caractère Unicode, sans limite de longueur.

Toutefois, si vous spécifiez explicitement une chaîne vide, le nom de l’OMI source est utilisé.

(optionnel) description : Une description pour la copie de l’OMI (par défaut, la même description que l’OMI source).

Cette description peut contenir n’importe quel caractère Unicode, sans limite de longueur.
endpoint : Le endpoint correspondant à la Région à laquelle vous voulez envoyer la requête. Pour en savoir plus, voir Installer et configurer AWS CLI.

La commande copy-image renvoie l’élément suivant :

ImageId : L’ID de la nouvelle OMI.

Résultat

{
    "ImageId": "ami-87654321"
}

Pages connexes

Méthodes API correspondantes

AWS™ et Amazon Web Services™ sont des marques de commerce d'Amazon Technologies, Inc. ou de ses affiliées aux États-Unis et/ou dans les autres pays.