October 4, 2022 . 1 MIN READ
While you can expect some performance degradation during this operation, it is highly recommended to test the impact in a development environment first. This ensures you aren’t caught off guard by latency spikes in production. However, if you schedule this change during off-peak hours, the impact should be manageable.
Here is a breakdown of the key concepts regarding your request:
RDS instances utilize a system of I/O credits to handle fluctuating workloads.
Baseline Performance: This is the steady-state speed your disk is guaranteed to provide based on its size.
Burst Performance: This allows the instance to “burst” above its baseline to meet sudden spikes in demand.
Credit Exhaustion: Burning through your credits isn’t necessarily a critical failure unless your application’s “normal” operation relies on that extra speed. You can monitor your credit balance via CloudWatch metrics to see how often you are dipping into them.
Increasing the disk size is an online operation.
Availability: There will not be a complete instance outage.
Performance: You will experience a temporary “performance hit” while the storage volume is being optimized.
Best Practice: To minimize the impact on your users, always perform storage modifications during your lowest traffic window.
Reference:
https://stackoverflow.com/questions/52204268/resize-amazon-rds-storage
