Create a snapshot

Last updated:2021-01-05 15:41:23

A snapshot is used to record data on an EBS volume at a specific time point. As data continues to be written to the EBS volume, snapshots can be created at any time and used as backups.


  • The snapshot feature is currently at the beta testing stage. You can create snapshots free of charge.
  • When a snapshot is being created based on an EBS volume, data changes on the EBS volume are not copied to the snapshot being created, and the incremental data generated by the operation after the snapshot is created will not be backed up to the snapshot;
  • The snapshot only backs up the data that has been written at the time of snapshot creation on the EBS volume, and does not back up the data that has not been written to the EBS volume in memory at that time. When a snapshot is created, there is data in the buffer that has not been written to the EBS volume, which will not be written to the snapshot or recovered from the snapshot. Therefore, it is strongly recommended that you shut down or make sure that the memory data has been written to the EBS volume before creating the snapshot, and pause the EBS volume reading and writing;
  • The first snapshot created for an EBS volume is a full snapshot. Subsequent snapshots created for the same EBS volume are all incremental snapshots.
  • The duration of the process of creating a snapshot based on an EBS volume depends on the capacity of the EBS volume.


  1. Log in to the KEC console.

  2. In the left navigation pane, choose Disk > EBS.

  3. On the EBS tab that appears, find the EBS volume for which you want to create a snapshot and choose Create Snapshot in the Operation column.

    Currently, only enhanced hard disk drive (EHDD) volumes and SSD volumes of EBS 3.0 support the snapshot feature.

  4. In the dialog box that appears, enter a name and description for the snapshot and click OK.

    The snapshot is created immediately.

Did you find the above information helpful?

Mostly Unhelpful
A little helpful
Very helpful

What might be the problems?

Unclear or awkward
Redundant or clumsy
Lack of context for the complex system or functionality

More suggestions


Please give us your feedback.


Thank you for your feedback.