Creates crash-consistent snapshots of multiple EBS volumes and stores the data in S3. Volumes are chosen by specifying an instance. Any attached volumes will produce one snapshot each that is crash-consistent across the instance. Boot volumes can be excluded by changing the parameters.
You can create multi-volume snapshots of instances in a Region and instances on an Outpost. If you create snapshots from an instance in a Region, the snapshots must be stored in the same Region as the instance. If you create snapshots from an instance on an Outpost, the snapshots can be stored on the same Outpost as the instance, or in the Region for that Outpost.
See also: AWS API Documentation
See ‘aws help’ for descriptions of global parameters.
create-snapshots
[--description <value>]
--instance-specification <value>
[--outpost-arn <value>]
[--tag-specifications <value>]
[--dry-run | --no-dry-run]
[--copy-tags-from-source <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
--description
(string)
A description propagated to every snapshot specified by the instance.
--instance-specification
(structure)
The instance to specify which volumes should be included in the snapshots.
InstanceId -> (string)
The instance to specify which volumes should be snapshotted.
ExcludeBootVolume -> (boolean)
Excludes the root volume from being snapshotted.
Shorthand Syntax:
InstanceId=string,ExcludeBootVolume=boolean
JSON Syntax:
{
"InstanceId": "string",
"ExcludeBootVolume": true|false
}
--outpost-arn
(string)
The Amazon Resource Name (ARN) of the AWS Outpost on which to create the local snapshots.
To create snapshots from an instance in a Region, omit this parameter. The snapshots are created in the same Region as the instance.
To create snapshots from an instance on an Outpost and store the snapshots in the Region, omit this parameter. The snapshots are created in the Region for the Outpost.
To create snapshots from an instance on an Outpost and store the snapshots on an Outpost, specify the ARN of the destination Outpost. The snapshots must be created on the same Outpost as the instance.
For more information, see Creating multi-volume local snapshots from instances on an Outpost in the Amazon Elastic Compute Cloud User Guide .
--tag-specifications
(list)
Tags to apply to every snapshot specified by the instance.
(structure)
The tags to apply to a resource when the resource is being created.
ResourceType -> (string)
The type of resource to tag. Currently, the resource types that support tagging on creation are:
capacity-reservation
|carrier-gateway
|client-vpn-endpoint
|customer-gateway
|dedicated-host
|dhcp-options
|egress-only-internet-gateway
|elastic-ip
|elastic-gpu
|export-image-task
|export-instance-task
|fleet
|fpga-image
|host-reservation
|image
|import-image-task
|import-snapshot-task
|instance
|internet-gateway
|ipv4pool-ec2
|ipv6pool-ec2
|key-pair
|launch-template
|local-gateway-route-table-vpc-association
|placement-group
|prefix-list
|natgateway
|network-acl
|network-interface
|reserved-instances
|route-table
|security-group
|snapshot
|spot-fleet-request
|spot-instances-request
|snapshot
|subnet
|traffic-mirror-filter
|traffic-mirror-session
|traffic-mirror-target
|transit-gateway
|transit-gateway-attachment
|transit-gateway-multicast-domain
|transit-gateway-route-table
|volume
|vpc
|vpc-peering-connection
|vpc-endpoint
(for interface and gateway endpoints) |vpc-endpoint-service
(for AWS PrivateLink) |vpc-flow-log
|vpn-connection
|vpn-gateway
.To tag a resource after it has been created, see CreateTags .
Tags -> (list)
The tags to apply to the resource.
(structure)
Describes a tag.
Key -> (string)
The key of the tag.
Constraints: Tag keys are case-sensitive and accept a maximum of 127 Unicode characters. May not begin with
aws:
.Value -> (string)
The value of the tag.
Constraints: Tag values are case-sensitive and accept a maximum of 255 Unicode characters.
Shorthand Syntax:
ResourceType=string,Tags=[{Key=string,Value=string},{Key=string,Value=string}] ...
JSON Syntax:
[
{
"ResourceType": "client-vpn-endpoint"|"customer-gateway"|"dedicated-host"|"dhcp-options"|"egress-only-internet-gateway"|"elastic-ip"|"elastic-gpu"|"export-image-task"|"export-instance-task"|"fleet"|"fpga-image"|"host-reservation"|"image"|"import-image-task"|"import-snapshot-task"|"instance"|"internet-gateway"|"key-pair"|"launch-template"|"local-gateway-route-table-vpc-association"|"natgateway"|"network-acl"|"network-interface"|"network-insights-analysis"|"network-insights-path"|"placement-group"|"reserved-instances"|"route-table"|"security-group"|"snapshot"|"spot-fleet-request"|"spot-instances-request"|"subnet"|"traffic-mirror-filter"|"traffic-mirror-session"|"traffic-mirror-target"|"transit-gateway"|"transit-gateway-attachment"|"transit-gateway-connect-peer"|"transit-gateway-multicast-domain"|"transit-gateway-route-table"|"volume"|"vpc"|"vpc-peering-connection"|"vpn-connection"|"vpn-gateway"|"vpc-flow-log",
"Tags": [
{
"Key": "string",
"Value": "string"
}
...
]
}
...
]
--dry-run
| --no-dry-run
(boolean)
Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is
DryRunOperation
. Otherwise, it isUnauthorizedOperation
.
--copy-tags-from-source
(string)
Copies the tags from the specified volume to corresponding snapshot.
Possible values:
volume
--cli-input-json
| --cli-input-yaml
(string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton
. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml
.
--generate-cli-skeleton
(string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input
, prints a sample input JSON that can be used as an argument for --cli-input-json
. Similarly, if provided yaml-input
it will print a sample input YAML that can be used with --cli-input-yaml
. If provided with the value output
, it validates the command inputs and returns a sample output JSON for that command.
See ‘aws help’ for descriptions of global parameters.
Example 1: To create a multi-volume snapshot
The following create-snapshots
example creates snapshots of all volumes attached to the specified instance.
aws ec2 create-snapshots \
--instance-specification InstanceId=i-1234567890abcdef0 \
--description "This is snapshot of a volume from my-instance"
Output:
{
"Snapshots": [
{
"Description": "This is a snapshot of a volume from my-instance",
"Tags": [],
"Encrypted": false,
"VolumeId": "vol-0a01d2d5a34697479",
"State": "pending",
"VolumeSize": 16,
"StartTime": "2019-08-05T16:58:19.000Z",
"Progress": "",
"OwnerId": "123456789012",
"SnapshotId": "snap-07f30e3909aa0045e"
},
{
"Description": "This is a snapshot of a volume from my-instance",
"Tags": [],
"Encrypted": false,
"VolumeId": "vol-02d0d4947008cb1a2",
"State": "pending",
"VolumeSize": 20,
"StartTime": "2019-08-05T16:58:19.000Z",
"Progress": "",
"OwnerId": "123456789012",
"SnapshotId": "snap-0ec20b602264aad48"
},
...
]
}
Example 2: To create a multi-volume snapshot with tags from the source volume
The following create-snapshots
example creates snapshots of all volumes attached to the specified instance and copies the tags from each volume to its corresponding snapshot.
aws ec2 create-snapshots \
--instance-specification InstanceId=i-1234567890abcdef0 \
--copy-tags-from-source volume \
--description "This is snapshot of a volume from my-instance"
Output:
{
"Snapshots": [
{
"Description": "This is a snapshot of a volume from my-instance",
"Tags": [
{
"Key": "Name",
"Value": "my-volume"
}
],
"Encrypted": false,
"VolumeId": "vol-02d0d4947008cb1a2",
"State": "pending",
"VolumeSize": 20,
"StartTime": "2019-08-05T16:53:04.000Z",
"Progress": "",
"OwnerId": "123456789012",
"SnapshotId": "snap-053bfaeb821a458dd"
}
...
]
}
Example 3: To create a multi-volume snapshot not including the root volume
The following create-snapshots
example creates a snapshot of all volumes attached to the specified instance except for the root volume.
aws ec2 create-snapshots \
--instance-specification InstanceId=i-1234567890abcdef0,ExcludeBootVolume=true
Example 4: To create a multi-volume snapshot and add tags
The following create-snapshots
example creates snapshots of all volumes attached to the specified instance and adds two tags to each snapshot.
aws ec2 create-snapshots \
--instance-specification InstanceId=i-1234567890abcdef0
--tag-specifications ResourceType=snapshot,Tags=[{Key=Name,Value=backup},{Key=costcenter,Value=123}]
Snapshots -> (list)
List of snapshots.
(structure)
Information about a snapshot.
Description -> (string)
Description specified by the CreateSnapshotRequest that has been applied to all snapshots.
Tags -> (list)
Tags associated with this snapshot.
(structure)
Describes a tag.
Key -> (string)
The key of the tag.
Constraints: Tag keys are case-sensitive and accept a maximum of 127 Unicode characters. May not begin with
aws:
.Value -> (string)
The value of the tag.
Constraints: Tag values are case-sensitive and accept a maximum of 255 Unicode characters.
Encrypted -> (boolean)
Indicates whether the snapshot is encrypted.
VolumeId -> (string)
Source volume from which this snapshot was created.
State -> (string)
Current state of the snapshot.
VolumeSize -> (integer)
Size of the volume from which this snapshot was created.
StartTime -> (timestamp)
Time this snapshot was started. This is the same for all snapshots initiated by the same request.
Progress -> (string)
Progress this snapshot has made towards completing.
OwnerId -> (string)
Account id used when creating this snapshot.
SnapshotId -> (string)
Snapshot id that can be used to describe this snapshot.
OutpostArn -> (string)
The ARN of the AWS Outpost on which the snapshot is stored. For more information, see EBS Local Snapshot on Outposts in the Amazon Elastic Compute Cloud User Guide .