Pause and Resume Workloads on T3 and T3a Instances with Amazon EC2 Hibernation
You can now hibernate newly-launched EBS-backed Amazon EC2 T3 and T3a 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.
You can now hibernate newly-launched EBS-backed Amazon EC2 T3 and T3a 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.
Hibernation saves effort in setting up the applications from scratch, saves time by reducing the bootstrapping time taken by applications, and saves cost by pausing the EC2 instances when not required. By using Hibernation, you can maintain a fleet of pre-warmed instances to get to a productive state faster without modifying your existing applications.
Hibernation is available for On-Demand Instances running on C3, C4, C5, I3, M3, M4, M5, M5a, M5ad, R3, R4, R5, R5a, R5ad, T2, T3, and T3a 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 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 technical documentation.
Modified 10/26/2021 – In an effort to ensure a great experience, expired links in this post have been updated or removed from the original post.