v8.0.0

Notice

This release will replace 7.3.0 and 7.3.1 as a major release to highlight the changes as described below.

What's Changed

• feat: Upgrade storage type by @timckt in #181
• feat: 🎸 add instance reboot permissions by @sj-williams in #184
• chore: Bump RDS example module reference by @timckt in #182
• chore: update example module version by @timckt in #180

Full Changelog: 7.3.0...8.0.0

New features

• Default Storage Type Upgrade

  • The default storage type has been upgraded from gp2 to gp3.

• Terraform Precondition Validation

  • Implemented Terraform precondition validation for storage type, storage size, and IOPS combinations for RDS instances using gp3 and io2 storage types.

• New Permission: Reboot RDS Instances via Service Pod

  • Users now have the permission to reboot their RDS instances directly through the service pod.

Important Note:

For all RDS DB engines except RDS for SQL Server, the baseline storage performance for gp3 volumes increases when the storage size reaches certain thresholds. When you upgrade the module and switch to gp3, you may need to adjust the db_iops value to ensure optimal performance, especially for RDS instances with large volumes.

Please pay special attention to this when upgrading your RDS instances, ensuring that the db_iops parameter aligns with the new baseline performance levels associated with your storage size.

`gp3` Storage Type

| Database Engine                 | Storage Size (GiB)   | Baseline Storage Performance    | Range of Provisioned IOPS  | Range of Provisioned Storage Throughput |
|---------------------------------|----------------------|---------------------------------|----------------------------|-----------------------------------------|
| Db2, MariaDB, MySQL, PostgreSQL | 20–399               | 3,000 IOPS / 125 MiB/s          | N/A                        | N/A                                     |
| Db2, MariaDB, MySQL, PostgreSQL | 400–65,536           | 12,000 IOPS / 500 MiB/s         | 12,000–64,000 IOPS         | 500–4,000 MiB/s                         |
| Oracle                          | 20–199               | 3,000 IOPS / 125 MiB/s          | N/A                        | N/A                                     |
| Oracle                          | 200–65,536           | 12,000 IOPS / 500 MiB/s         | 12,000–64,000 IOPS         | 500–4,000 MiB/s                         |
| SQL Server                      | 20–16,384            | 3,000 IOPS / 125 MiB/s          | 3,000–16,000 IOPS          | 125–1,000 MiB/s                         |

`io2` Storage Type

| Database Engine                 | Storage Size (GiB)   | Range of Provisioned IOPS       | Maximum Throughput         |
|---------------------------------|----------------------|---------------------------------|----------------------------|
| Db2, MariaDB, MySQL, PostgreSQL | 100–65,536           | 1,000–256,000 IOPS              | 16,000 MiB/s               |
| Oracle                          | 100–199              | 1,000–199,000 IOPS              | 16,000 MiB/s               |
| Oracle                          | 200–65,536           | 1,000–256,000 IOPS              | 16,000 MiB/s               |
| SQL Server                      | 20–65,536            | 1,000–256,000 IOPS              | 16,000 MiB/s               |

For more information about the RDS storage type, storage size, and IOPS combinations, please refer to our user guide here.

Action Required

• Review and Adjust db_iops Parameter

  • When upgrading to this new version, review your current storage size and adjust the db_iops parameter as needed to meet the new baseline performance levels.

• Test in Non-Production Environments

  • Before applying changes to production environments, thoroughly test the new module version in non-production namespaces to ensure compatibility and performance.