v7.2.2

This release replaces 7.2.0 & 7.2.1 releases for AWS provider bump.

relates to ministryofjustice/cloud-platform#6517

Full Changelog: 7.2.1...7.2.2

v8.0.1

What's Changed

• Bump terraform-docs/gh-actions from 1.2.0 to 1.3.0 by @dependabot in #183
• ci: 🎡 action by @jaskaransarkaria in #186
• chore: 🤖remove aws provider version, fix output syntax by @sj-williams in #187

Patch release for aws provider v5.x.x compatible db_name attribute

Full Changelog: 7.3.1...8.0.1

v7.2.1

Full Changelog: 7.2.0...7.2.1

Note:

This release is intended as a step release for 7.2.* module users to have access to DB reboot IAM permissions, ahead of our planned full environments bump to 7.3.*

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.

v7.3.1

What's Changed

• chore: Bump RDS example module reference by @timckt in #182
• feat: 🎸 add instance reboot permissions by @sj-williams in #184

Full Changelog: 7.3.0...7.3.1

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.

7.3.0

What's Changed

• chore: update example module version by @timckt in #180
• feat: Upgrade storage type by @timckt in #181

Full Changelog: 7.2.0...7.3.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.

v7.2.0

What's Changed

Add data block for new EKS specific subnet security group rules additions

Relates to relates to ministryofjustice/cloud-platform#6030

• docs: ✏️ update examples for module update by @sj-williams in #177

Full Changelog: 7.1.0...7.2.0

v7.1.0

What's Changed

• chore: Bump example files by @timckt in #175
• chore: 🤖 fix conditional check for replica db name and engine version by @sj-williams in #176

Full Changelog: 6.1.0...7.1.0

v7.0.0

What's Changed

• update some README contents by @timckt in #163
• 🔧 Bump example files to use latest release by @kyphutruong in #164
• allow users know when to enable and disable performance insights by @FolarinOyenuga in #169
• Fix version rds-postgresql.tf by @davidread in #170
• feat: add dependabot to cloud platform project workflow by @mikebell in #171
• Bump terraform-docs/gh-actions from 1.0.0 to 1.2.0 by @dependabot in #172
• feat: Update ca cert identifier by @timckt in #174

New Contributors

• @timckt made their first contribution in #163
• @FolarinOyenuga made their first contribution in #169
• @davidread made their first contribution in #170
• @mikebell made their first contribution in #171

Full Changelog: 6.0.2...7.0.0

6.0.2

What's Changed

• 🐛 Fixing permissions to allow CP Users to list RDS Engine options and engines by @kyphutruong in #162

New Contributors

• @kyphutruong made their first contribution in #162

Full Changelog: 6.0.1...6.0.2