-
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
r/aws_fsx_openzfs_file_system increase SINGLE_AZ_2 max IOPS to 400000 #40359
r/aws_fsx_openzfs_file_system increase SINGLE_AZ_2 max IOPS to 400000 #40359
Conversation
Community NoteVoting for Prioritization
For Submitters
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀.
@brinnjoyce Thanks for the contribution 🎉 👏. |
This functionality has been released in v5.79.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! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Increases the aws_fsx_openzfs_file_system SINGLE_AZ_2 max valid IOPS to 400000 to match what's supported by AWS and allow the terraform provider to work with larger filesystems which force IOPS to be above the current 350000 limit of the provider.
Relations
Closes #40358
References
Reference for max IOPS https://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/performance.html#zfs-fs-performance
Output from Acceptance Testing
Let me know if I need to run the tests myself and I can try to arrange a sandbox account.