Skip to main content

OpenSearch: Migrate volume from GP2 to GP3

Difficulty: Easy

Description

We identified several OpenSearch domains in your account that use gp2 storage volumes. GP3 is a newer generation of EBS storage that offers similar performance at a lower cost than gp2. Not all instances are eligible for gp3 migration.


Selection Criteria

  • The OpenSearch node uses gp2 storage volumes.

  • The OpenSearch instance type supports gp3 migration.


Expected Saving

~10% reduction in EBS storage costs for each migrated volume.

Volume type

Price (us-east-1)

Baseline IOPS

gp2

$0.135/GB-month

3 IOPS/GB (burst to 3,000)

gp3

$0.122/GB-month

3,000 IOPS flat

Example: 1 TB gp2 volume costs $135/month → ~$122/month on gp3 = $156/year saved per TB, with better baseline performance included at no extra cost.


Operational Impact

  • In-place migration: AWS OpenSearch performs the EBS volume type migration in-place. Multi-AZ domains experience no client-visible downtime — replicas ensure continuity during the migration. Single-AZ domains may have a brief interruption.

  • Duration: migration time scales with the total volume size. Large domains (hundreds of GB per node) may take several hours. The domain status shows as "Processing" during migration.

  • Instance compatibility: not all OpenSearch instance types support gp3 storage. If the node runs on an incompatible instance type, an instance modernization must be performed first. Refer to the requiresInstanceModernization column in the recommendation.

  • IOPS provisioning: gp3 provides a flat 3,000 IOPS baseline per volume at no extra cost. Additional IOPS beyond the baseline can be provisioned at an extra charge if your workload requires it.

  • Recovery: reverting to gp2 is possible via another volume type modification — no data loss, but another migration cycle is required.


References

Did this answer your question?