- Newest
- Most votes
- Most comments
Here are the key points regarding the transition from GP2 to GP3 storage for your Amazon RDS database:
-
Bottleneck and Metrics:
The main bottleneck for GP3 volumes is the EBSByteBalance metric, which represents the percentage of throughput credits available. You should monitor the EBSByteBalance metric to ensure your workload does not exceed the provisioned throughput.
-
Provisioning GP3 Storage:
With GP3, you can provision the desired IOPS (up to 16,000) and throughput (up to 1,000 MiB/s) independently of the storage size. For RDS for SQL Server, you can provision additional IOPS and throughput for any available storage size. You pay only for the additional provisioned IOPS and throughput beyond the baseline of 3,000 IOPS and 125 MiB/s.
-
Handling Capacity Needs:
If the EBSByteBalance metric approaches a critical level, you can increase the provisioned throughput by modifying the RDS instance. The cost for additional provisioned throughput is $0.04 per provisioned MiB/s-month.
-
Transition Process:
Transitioning from GP2 to GP3 storage is a straightforward process and does not involve any downtime or reboot. The RDS instance will enter a "Storage Optimization" state during the transition, but it will remain accessible and you can continue regular operations.
Relevant content
- asked a year ago
- Accepted Answerasked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you. Finaly clear info.