-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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 support for Redshift Multi-AZ deployment #34926
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Related #32180 Looks like this is technically a duplicate of ☝️ , but given that there's a new development (this feature is now GA'd), leaving this one open to maintain the great references. |
This functionality has been released in v5.35.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 issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Redshift Multi-AZ is generally available since Nov 1st, 2023 - https://aws.amazon.com/about-aws/whats-new/2023/11/amazon-redshift-multi-az-ra3-clusters/. The ability to configure Multi-AZ is missing in aws_redshift_cluster resource. This should be added to the functionality and arguments of this resource.
Affected Resource(s) and/or Data Source(s)
aws_redshift_cluster
Potential Terraform Configuration
References
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: