-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update storage/volume types from gp2 to gp3 across all plans #255
Comments
ill test changing plans and start investigating the difference for a little spare fuin |
Following issues are a blocked for now hashicorp/terraform-provider-aws#28271 |
fixed issues, pull request for changes are here |
found bugs, will update when working |
hashicorp/terraform-provider-aws#28160 blocked issue for now |
@JasonTheMain you should not have any more blocker to adopt gp3. If using: https://github.com/terraform-aws-modules/terraform-aws-rds use the last version: Default values have been fixed, allowing a smooth transition to gp3. |
Closing this and opening #271 to handle converting existing databases to gp3 |
closed per #330 |
In order to optimize costs, we should update EBS storage from gp2 to gp3 volumes across all of our brokered plans
Security considerations
There are no meaningful security differences from gp2 to gp3 volumes, as far as I know, just cost and performance optimizations.
https://aws.amazon.com/ebs/general-purpose/#:~:text=gp3%20offers%20SSD%2Dperformance%20at,improving%20performance%20and%20reducing%20costs.
Implementation sketch
storage_type
instead of gp2volumeType
instead of gp2The text was updated successfully, but these errors were encountered: