Amazon OpenSearch Service · Finder

OpenSearch Retype Gp2ToGp3

gp2gp3

Convert OpenSearch GP2 volumes to GP3 for 20% storage savings with better performance. CloudFix identifies eligible domains and migrates volumes.

Reported by the finder
Effort: Medium
Action: Retype
Amazon OpenSearch Service

What happens, in order.

Finder · read-only
Finds the opportunity
Scans your connected accounts with a read-only role. It can see resource metadata and usage; it can’t change anything.
Report
Reported to you
It appears in your Recommendations view with what it would save. The change is yours to make.

Finder role

Read-only. It can see resource metadata and usage. It can’t change anything.

Fixer role

Not used here: this one is reported by the finder, so the change is yours to make.

Saves by

This finder identifies OpenSearch domains using GP2 volumes for storage and recommends changing these volumes to GP3. GP3 volumes offer better performance and lower cost compared to GP2 volumes, making this change beneficial for cost optimization and potentially enhancing performance.

Are you paying more than necessary for your Amazon OpenSearch Service storage? This CloudFix Finder identifies OpenSearch domains using GP2 EBS volumes and recommends changing to GP3 volumes, which offer better performance at a lower cost. This simple volume type change can reduce your storage costs while potentially improving your domain’s performance.

Overview

Problem Statement

Many Amazon OpenSearch Service domains were created using GP2 (General Purpose SSD) EBS volumes as their storage option. While GP2 was the default choice for years, AWS now offers GP3 volumes, which provide better baseline performance and lower costs. Customers continuing to use GP2 volumes are missing out on both cost savings and performance improvements.

Solution

CloudFix identifies OpenSearch domains using GP2 volumes and recommends migrating to GP3. When comparing the two volume types:

GP3 volumes are approximately 20% less expensive than GP2 volumes
GP3 volumes provide baseline performance of 3,000 IOPS and 125 MB/s throughput regardless of volume size
GP3 allows independent scaling of IOPS and throughput, unlike GP2 where performance is tied to volume size

While this feature doesn’t include an automatic fixer, CloudFix provides guidance on implementing this change manually through the AWS Console, AWS CLI, or Infrastructure as Code tools.

AWS Services Affected

Amazon OpenSearch Service

How It Works

CloudFix uses your cost and usage data to find, read-only, the OpenSearch domains still storing data on GP2 volumes. Each opportunity appears in your Recommendations with the domain, its current storage configuration, a recommended GP3 configuration with equivalent or better performance, and the estimated annual savings.

This feature does not include an automatic Fixer. The change is a domain configuration update that may trigger a blue/green deployment, and you may want to tune IOPS and throughput for your workload, so you make the change yourself at a time that suits you: in the OpenSearch Service console, with the AWS CLI, or in your CloudFormation, Terraform or CDK templates.

FAQ

Will changing from GP2 to GP3 cause any downtime?

The change may trigger a blue/green deployment, which does not cause downtime but does involve a synchronization period. During this period, write operations might experience slightly higher latency as changes are propagated to the new configuration.

Is there any risk of data loss when changing volume types?

No, the change from GP2 to GP3 does not inherently risk data loss. The blue/green deployment process ensures data integrity during the migration. However, as with any significant infrastructure change, having recent snapshots is advisable.

How do I determine the right IOPS and throughput values for GP3?

When migrating from GP2 to GP3, CloudFix recommends IOPS and throughput values that match or exceed your current GP2 performance. You can also analyze CloudWatch metrics for your domain to understand actual IOPS and throughput utilization and optimize accordingly.

Can I modify IOPS and throughput settings after migrating to GP3?

Yes, one advantage of GP3 volumes is the ability to independently adjust IOPS and throughput without changing volume size. You can modify these settings after migration based on observed performance needs.

Why doesn’t CloudFix automatically implement this change?

The migration requires a domain update that triggers a blue/green deployment process. Since this involves a synchronization period and potential temporary impact on write performance, CloudFix provides the recommendation but leaves the implementation to the user to schedule at an appropriate time.

Ready to start saving on AWS? See how much you could cut from your cloud bill with a free cost optimization assessment, or explore CloudFix automated Finder/Fixers that eliminate waste across 30+ AWS services.

Browse all 110+ finders

See whether this one applies to your account.

A free savings assessment reports which fixers can be applied to your environment. Results typically within 24 hours.

Get a free savings assessment See how CloudFix works

What happens, in order.

Finds the opportunity

Reported to you