Prerequisites for Amazon EC2 instance hibernation - Amazon Elastic Compute Cloud

Prerequisites for Amazon EC2 instance hibernation

You can enable hibernation support for an On-Demand Instance or a Spot Instance when you launch it. You can't enable hibernation on an existing instance, whether it is running or stopped. For more information, see Enable instance hibernation.

AWS Regions

You can use hibernation with instances in all AWS Regions.

AMIs

You must use an HVM AMI that supports hibernation. The following AMIs support hibernation:

  • AL2023 AMI released 2023.09.20 or later

  • Amazon Linux 2 AMI released 2019.08.29 or later

  • Amazon Linux AMI 2018.03 released 2018.11.16 or later

  • CentOS version 8 AMI ¹

  • Fedora version 34 or later AMI ¹

  • Red Hat Enterprise Linux (RHEL) 9 AMI ¹

  • Red Hat Enterprise Linux (RHEL) 8 AMI ¹

  • Ubuntu 22.04.2 LTS (Jammy Jellyfish) AMI released with serial number 20230303 or later ²

  • Ubuntu 20.04 LTS (Focal Fossa) AMI released with serial number 20210820 or later ²

  • Ubuntu 18.04 LTS (Bionic Beaver) AMI released with serial number 20190722.1 or later ² ⁴

  • Ubuntu 16.04 LTS (Xenial Xerus) AMI ² ³ ⁴

 

¹ For CentOS, Fedora, and Red Hat Enterprise Linux, hibernation is supported on Nitro-based instances only.

² We recommend disabling KASLR on instances with Ubuntu 22.04.2 LTS (Jammy Jellyfish), Ubuntu 20.04 LTS (Focal Fossa), Ubuntu 18.04 LTS (Bionic Beaver), and Ubuntu 16.04 LTS (Xenial Xerus).

³ For the Ubuntu 16.04 LTS (Xenial Xerus) AMI, hibernation is not supported on t3.nano instance types. No patch will be made available because Ubuntu (Xenial Xerus) ended support in April 2021. If you want to use t3.nano instance types, we recommend that you upgrade to the Ubuntu 22.04.2 LTS (Jammy Jellyfish), Ubuntu 20.04 LTS (Focal Fossa) AMI, or the Ubuntu 18.04 LTS (Bionic Beaver) AMI.

⁴ Support for Ubuntu 18.04 LTS (Bionic Beaver) and Ubuntu 16.04 LTS (Xenial Xerus) has reached end of life.

Support for other versions of Ubuntu and other operating systems is coming soon.

  • Windows Server 2022 AMI released 2023.09.13 or later

  • Windows Server 2019 AMI released 2019.09.11 or later

  • Windows Server 2016 AMI released 2019.09.11 or later

  • Windows Server 2012 R2 AMI released 2019.09.11 or later

  • Windows Server 2012 AMI released 2019.09.11 or later

Instance families

You must use an instance family that supports hibernation.

  • General purpose: M3, M4, M5, M5a, M5ad, M5d, M6i, M6id, M7i, M7i-flex, T2, T3, T3a

  • Compute optimized: C3, C4, C5, C5d, C6i, C6id, C7a, C7i, C7i-flex

  • Memory optimized: R3, R4, R5, R5a, R5ad, R5d, R7a, R7i, R7iz

  • Storage optimized: I3, I3en

Nitro instances – Bare metal instances are not supported.

To see the available instance types that support hibernation in a specific Region

The available instance types vary by Region. To see the available instance types that support hibernation in a Region, use the describe-instance-types command with the --region parameter. Include the --filters parameter to scope the results to the instance types that support hibernation and the --query parameter to scope the output to the value of InstanceType.

aws ec2 describe-instance-types --filters Name=hibernation-supported,Values=true --query "InstanceTypes[*].[InstanceType]" --output text | sort

Example output

c3.2xlarge c3.4xlarge c3.8xlarge c3.large c3.xlarge c4.2xlarge c4.4xlarge c4.8xlarge ...

Instance RAM size

Linux instances – Must be less than 150 GB.

Windows instances – Can be up to 16 GB. For hibernating a T3 or T3a Windows instance, we recommend at least 1 GB of RAM.

Root volume type

The root volume must be an EBS volume, not an instance store volume.

Root volume size

The root volume must be large enough to store the RAM contents and accommodate your expected usage, for example, OS or applications. If you enable hibernation, space is allocated on the root volume at launch to store the RAM.

Root volume encryption

The root volume must be encrypted to ensure the protection of sensitive content that is in memory at the time of hibernation. When RAM data is moved to the EBS root volume, it is always encrypted. Encryption of the root volume is enforced at instance launch.

Use one of the following three options to ensure that the root volume is an encrypted EBS volume:

  • EBS encryption by default – You can enable EBS encryption by default to ensure that all new EBS volumes created in your AWS account are encrypted. This way, you can enable hibernation for your instances without specifying encryption intent at instance launch. For more information, see Enable encryption by default.

  • EBS "single-step" encryption – You can launch encrypted EBS-backed EC2 instances from an unencrypted AMI and also enable hibernation at the same time. For more information, see Use encryption with EBS-backed AMIs.

  • Encrypted AMI – You can enable EBS encryption by using an encrypted AMI to launch your instance. If your AMI does not have an encrypted root snapshot, you can copy it to a new AMI and request encryption. For more information, see Encrypt an unencrypted image during copy and Copy an AMI.

EBS volume type

The EBS volumes must use one of the following EBS volume types:

  • General Purpose SSD (gp2 and gp3)

  • Provisioned IOPS SSD (io1 and io2)

If you choose a Provisioned IOPS SSD volume type, you must provision the EBS volume with the appropriate IOPS to achieve optimum performance for hibernation. For more information, see Amazon EBS volume types in the Amazon EBS User Guide.

Spot Instance requests

For Spot Instances, the following requirements apply:

  • The Spot Instance request type must be persistent.

  • You can't specify a launch group in the Spot Instance request.