Chore: Update deprecated default M4 type to M5 #328
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
On the 29th of March, AWS has disabled new creation of M4 type instances of RDS. Instead, the recommendation to use M5 type instances.
https://repost.aws/articles/AR_Rw2Xbe5Q9O1ZPKbU5S4Mg/amazon-rds-for-sql-server-is-ending-support-for-m4-r4-and-t2-database-instances-on-march-29-2024
In this PR we update the db size default value.
How has this been tested
I did not test it directly, but instead, verified that there are no orderable options for "db.m4.xlarge"
and that on the other hand, there are plenty options with "db.m5.xlarge", including the current default version 12.15.