Posted On: Sep 5, 2019
We are excited to announce the availability of the EC2 Hibernation feature in Amazon Web Services China (Beijing) Region, operated by Sinnet, and the Amazon Web Services China (Ningxia) Region, operated by NWCD.
Hibernation gives you the ability to launch EC2 instances, set them up as desired, hibernate them, and then quickly bring them back to life when you need them. Applications pick up exactly where they left off instead of rebuilding their memory footprint. Using hibernation, you can maintain a fleet of pre-warmed instances that can get to a productive state faster, and you can do this without modifying your existing applications.
Hibernation requires an EC2 instance to be an encrypted Amazon EBS-backed instance. This ensures protection of sensitive contents in memory (RAM) as they get copied to EBS upon hibernation. You can now enable Amazon EBS Encryption by Default, to ensure all new EBS volumes created in your account are encrypted. You no longer have to create an encrypted copy of the Amazon Machine Image (AMI) before launching an instance. Alternatively, you can also now specify encryption intent at launch (with unencrypted AMI or snapshot) and enable hibernation at the same time.
Hibernation is available for On-Demand and Reserved Instances running on newly launched M3, M4, M5, C3, C4, C5, R3, R4, and R5 instances with memory (RAM) of less than 150 GB running Amazon Linux, Amazon Linux 2 and Ubuntu Server 18.04 LTS.
Hibernation is also available for Spot Instances running on newly launched M4, M5, C3, C4, C5, R3, R4 instances with memory (RAM) of less than 100 GB running Amazon Linux 2, Amazon Linux, Ubuntu and Microsoft Windows.
This feature is available through Amazon Command Line Interface (CLI), Amazon SDKs, or the Amazon Web Services Management Console at no extra charge. To learn more about hibernation, visit this blog. For information about enabling hibernation for your EC2 instances, visit our FAQs or technical documentation. For more information about EBS Encryption by Default, visit the technical documentation.