import { _DiskMap } from "./_DiskMap"; import { _Tag } from "./_Tag"; import { BrowserHttpOptions as __HttpOptions__ } from "@aws-sdk/types"; import * as __aws_sdk_types from "@aws-sdk/types"; /** * CreateInstancesFromSnapshotInput shape */ export interface CreateInstancesFromSnapshotInput { /** *
The names for your new instances.
*/ instanceNames: ArrayAn object containing information about one or more disk mappings.
*/ attachedDiskMapping?: { [key: string]: Array<_DiskMap> | Iterable<_DiskMap>; } | Iterable<[string, Array<_DiskMap> | Iterable<_DiskMap>]>; /** *The Availability Zone where you want to create your instances. Use the following formatting: us-east-2a (case sensitive). You can get a list of Availability Zones by using the get regions operation. Be sure to add the include Availability Zones parameter to your request.
The name of the instance snapshot on which you are basing your new instances. Use the get instance snapshots operation to return information about your existing snapshots.
*/ instanceSnapshotName: string; /** *The bundle of specification information for your virtual private server (or instance), including the pricing plan (e.g., micro_1_0).
You can create a launch script that configures a server with additional user data. For example, apt-get -y update.
Depending on the machine image you choose, the command to get software on your instance varies. Amazon Linux and CentOS use yum, Debian and Ubuntu use apt-get, and FreeBSD uses pkg. For a complete list, see the Dev Guide.
The name for your key pair.
*/ keyPairName?: string; /** *The tag keys and optional values to add to the resource during create.
To tag a resource after it has been created, see the tag resource operation.