Skip to content

Which EBS Volume Initialization Option Should I Choose for My Volume Created from a Snapshot?

5 minute read
Content level: Foundational
0

When you create an Amazon EBS volume from a snapshot (or volume copy), data blocks must be written to the volume before you can access them. During initialization, you may experience increased I/O latency and decreased performance.

To address this, AWS provides three initialization options. Each suits different scenarios and the right choice depends on multiple factors such as timing, scale, whether the volume already exists, performance tier, cost etc.

Short description

By default, the volume initialization rate fluctuates throughout the initialization process, which could make completion times unpredictable. Three initialization options to address this are:

  • Amazon EBS Provisioned Rate for Volume Initialization
  • Fast Snapshot Restore (FSR)
  • Manual Initialization (fio or dd)

Note: Provisioned Rate and FSR are not supported for volume copies. For more information, see Volume copy initialization.

Resolution

Key Questions to Identify your Scenario:

  • Has the volume already been created and attached?
  • Do you need instant full performance at the moment of volume creation?
  • Do you have time to plan ahead and pre-enable features on your snapshot?
  • Are you creating volumes in a burst (many at once)?
  • Is the volume provisioned above 64000 IOPS or 1000 MiB/s throughput?
  • Is cost a primary concern?

The answers to the above questions will guide you to the right option below.

1. Amazon EBS Provisioned Rate for Volume Initialization

Choose this when:

  • You are creating a new volume from a snapshot and need it initialized within a predictable, calculable timeframe
  • You are launching multiple volumes simultaneously and need all of them ready within a defined window
  • You need to initialize volumes from a snapshot larger than 16 TiB (which exceeds the FSR limit)
  • You cannot use Fast Snapshot Restore because:
    • You don't have time to enable FSR and wait for credits to accumulate
    • Your snapshot is too large for FSR credits to replenish at the rate you need
    • You exhausted FSR credits from a burst of volume creations

Not suitable when:

  • The volume has already been created (rate must be specified at creation time)
  • You are creating volumes on AWS Outposts, Local Zones, or Wavelength Zones
  • You are creating a volume copy (not supported)

Key considerations:

  • You can specify a rate between 100 and 300 MiB/s
  • Initialization time is based on the size of the snapshot data, not the volume size.
  • The default cumulative quota is 5000 MiB/s across concurrent requests per Region. Requests exceeding this limit or hitting capacity constraints will fail, but the quota is adjustable. See Amazon EBS quotas
  • If you specify a Provisioned Rate on a volume created from an FSR-enabled snapshot, the Provisioned Rate takes precedence and FSR is not used

For implementation details, billing, and quotas, see Initialize Amazon EBS volumes.

2. Fast Snapshot Restore (FSR)

Choose this when:

  • You need instant full performance the moment a volume is created
  • You can plan ahead and enable FSR on your snapshot before creating volumes

Not suitable when:

  • The volume has already been created
  • Your snapshot exceeds 16 TiB
  • You cannot plan ahead (FSR must be enabled on the snapshot before volume creation)
  • You are creating volumes on AWS Outposts, Local Zones, or Wavelength Zones
  • You are creating a volume copy (not supported)
  • You also specify a Provisioned Rate (Provisioned Rate takes precedence, overriding FSR)

Key considerations:

  • FSR uses a credit-based system. The number of volumes that receive the full performance benefit of FSR is determined by volume creation credits for the snapshot.
  • FSR is enabled per snapshot per Availability Zone. Plan your AZ selection accordingly
  • Default quota is 5 snapshots per Region with FSR enabled (includes shared snapshots). This is adjustable
  • If using shared snapshots, enabling FSR on them counts against your quota, not the snapshot owner's
  • FSR is not inherited. New snapshots created from FSR-enabled volumes, or copies of FSR-enabled snapshots, do not automatically get FSR. You must explicitly enable it on each snapshot
  • Volumes provisioned with performance up to 64,000 IOPS and 1,000 MiB/s throughput receive the full performance benefit of fast snapshot restore. For volumes provisioned with performance greater than 64,000 IOPS or 1,000 MiB/s throughput, you may consider other options to initialize the volume to receive its full performance.

For implementation details, credit mechanics, and pricing, see Amazon EBS fast snapshot restore.

3. Manual Initialization (fio or dd)

Choose this when:

  • The volume has already been created and attached (Options 1 and 2 must be specified at creation time)
  • You want to avoid any additional billing charges
  • You are initializing a volume copy
  • Provisioned Rate or FSR are not available in your environment (Outposts, Local Zones, Wavelength Zones)

Not suitable when:

  • You need instant full performance
  • You need predictable, time-bound initialization

Key consideration:

  • fio is considerably faster because it allows multi-threaded reads.
  • While initializing Provisioned IOPS SSD (io1/io2) volumes created from snapshots, performance may drop below 50% of the expected level, causing a warning state in the I/O Performance status check. This is expected and can be safely ignored during initialization

For more details, see Initialize Amazon EBS volumes.


Quick Decision Guide:

  • Need predictable, time-bound initialization at scale → Provisioned Rate
  • Need instant full performance and can plan ahead → FSR
  • The volume already exists, or initializing a volume copy or need a no-cost option → Manual Initialization
AWS
EXPERT

published 8 days ago99 views