-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[Enhancement]: Add gp3 storage_type support to aws_db_instance #27702
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Hi @katdev, thanks for raising this issue. I'll pick it up 👍 |
The same issue lies in Ansible rds_instance module too. It is not supporting creation of new RDS instance when passing storage type as gp3. Any fixes for that ? |
You should probably ask that question in the Ansible repo :) |
Hello! What about this issue? Is somebody working on it? |
See this PR and comment: #27670 (review) My understanding is that @gdavison and his team might take over the PR that @erz4 started |
This functionality has been released in v4.45.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
talk about perfect timing! gp3 for rds is exactly what I wanted. |
Foremost, thanks a lot for bringing this change that quickly @ewbankkit, and @erz4 as well as everyone involved 👏 Sadly, it seems that there is a bug for existing RDS instances blocking the switch from gp2 to gp3, you will most likely be blocked by this error:
FYI, an issue already exists for this bug: #28160 Maybe you want to give your 👍 there, if this is also a blocker for you. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
As of November 4(ish), the gp3 storage type is now supported on RDS, but it's not yet supported by the latest version of the AWS provider. Attempting to specify gp3 results in:
Please add support to the AWS provider for this storage type, along with support for the advanced settings available with gp3,
Provisioned IOPS
andStorage throughput
.Affected Resource(s) and/or Data Source(s)
aws_db_instance
Potential Terraform Configuration
References
Announcement.
User guide.
Would you like to implement a fix?
No, thank you
The text was updated successfully, but these errors were encountered: