Posted On: Oct 22, 2020

You can now hibernate newly-launched EBS-backed Amazon EC2 I3, M5ad, and R5ad instances. Hibernation provides you with the convenience of pausing your workloads and resuming them later from the saved state. Hibernation is just like closing and opening your laptop lid — your application will start right from where it left off. By using hibernation, you can maintain a fleet of pre-warmed instances that can get to a productive state faster without modifying your existing applications.  

Upon hibernation, your instance’s EBS root volume and any attached EBS data volumes are persisted. The data from memory (RAM) is also saved to your EBS root volume. However, for any instance store volumes that are attached to the instance, the data on the instance store volumes is lost. When your hibernated instance is resumed, the EBS root volume is restored from its prior state, and the RAM content is reloaded. Previously attached data volumes are reattached, and the instance retains its instance ID. 

Hibernation is available for On-Demand Instances and Reserved Instances running on C3, C4, C5, I3, M3, M4, M5, M5a, M5ad, R3, R4, R5, R5a, R5ad, and T2 instances running Amazon Linux, Amazon Linux 2, Ubuntu 16.04 and 18.04 LTS, and Windows Server 2012, 2012R2, 2016, and 2019. For Windows, hibernation is supported for instances with up to 16 GB of RAM. For other operating systems, hibernation is supported for instances with less than 150 GB of RAM. 

This feature is available through AWS CloudFormation, AWS Management Console, or through the AWS SDKs, AWS Tools for Powershell or the AWS Command Line Interface (CLI). To learn more about hibernation, visit this blog. For information about enabling hibernation for your EC2 instances, visit our FAQs or User Guide