EC2 Boot Time Calculator

ready = provisioning + hydration + OS boot + user-data + warm-up, where hydration = AMI GB × 1024 ÷ restore MB/s unless Fast Snapshot Restore is on. An instance is not useful when EC2 reports it running — it is useful once the volume is hydrated, the OS is up, user-data has finished and the application has warmed. First-touch reads of a snapshot-backed volume stream from S3 at a limited rate, so a large AMI can dominate the whole sequence; Fast Snapshot Restore removes that term for a per-snapshot hourly fee. Baking dependencies into the AMI shortens user-data at the cost of a longer hydration.

Auto Scaling terminates instances that fail health checks after the grace period, so a grace period shorter than the real launch sequence produces an endless launch-and-kill loop under load.

This calculator takes 8 inputs: AMI data to hydrate, Snapshot restore throughput, Fast Snapshot Restore enabled, Instance provisioning and attach, Operating system boot, User-data and configuration, Application warm-up before full capacity, Health check grace period. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Shrink the AMI so there is less to hydrate, move package installs from user-data into the image, use a warm pool so instances are pre-booted and stopped, and reach for Fast Snapshot Restore only when a large image must launch cold at scale.