Hibernate your On-Demand Windows instance
When you hibernate an instance, Amazon EC2 signals the operating system to perform hibernation (suspend-to-disk). Hibernation saves the contents from the instance memory (RAM) to your Amazon Elastic Block Store (Amazon EBS) root volume. Amazon EC2 persists the instance's EBS root volume and any attached EBS data volumes. When you start your instance:
-
The EBS root volume is restored to its previous state
-
The RAM contents are reloaded
-
The processes that were previously running on the instance are resumed
-
Previously attached data volumes are reattached and the instance retains its instance ID
You can hibernate an instance only if it's enabled for hibernation and it meets the hibernation prerequisites.
If an instance or application takes a long time to bootstrap and build a memory footprint in order to become fully productive, you can use hibernation to pre-warm the instance. To pre-warm the instance, you:
-
Launch it with hibernation enabled.
-
Bring it to a desired state.
-
Hibernate it so that it's ready to be resumed to the desired state whenever needed.
You're not charged for instance usage for a hibernated instance when it is in the
stopped state. However, you are charged for instance usage while the
instance is in the stopping state, while the contents of the RAM are
transferred to the EBS root volume. (This is different from when you stop an instance without hibernating it.) You're not charged
for data transfer. However, you are charged for storage of any EBS volumes, including
storage for the RAM contents.
If you no longer need an instance, you can terminate it at any time, including when it is
in a stopped (hibernated) state. For more information, see Terminate your instance.
For information about using hibernation on Linux instances, see Hibernate your Linux instance in the Amazon EC2 User Guide for Linux Instances.
This topic describes how to hibernate On-Demand Instances (including those that may be covered by a Reserved Instance or a Capacity Reservation). For information about hibernating Spot Instances, see Hibernate interrupted Spot Instances.
Contents
