AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
When a snapshot is created, any AWS Marketplace product codes that are associated with the source volume are propagated to the snapshot.
You can take a snapshot of an attached volume that is in use. However, snapshots only
capture data that has been written to your EBS volume at the time the snapshot command
is issued; this may exclude any data that has been cached by any applications or the
operating system. If you can pause any file systems on the volume long enough to take
a snapshot, your snapshot should be complete. However, if you cannot pause all file
writes to the volume, you should unmount the volume from within the instance, issue
the snapshot command, and then remount the volume to ensure a consistent and complete
snapshot. You may remount and use your volume while the snapshot status is
To create a snapshot for EBS volumes that serve as root devices, you should stop the instance before taking the snapshot.
Snapshots that are taken from encrypted volumes are automatically encrypted. Volumes that are created from encrypted snapshots are also automatically encrypted. Your encrypted volumes and any associated snapshots always remain protected.
Version: (assembly version)
public virtual CreateSnapshotResponse CreateSnapshot( CreateSnapshotRequest request )
Container for the necessary parameters to execute the CreateSnapshot service method.
Supported in: 4.5, 4.0, 3.5