Skip to content

Allow aurora to scale#2110

Merged
cadmiumcat merged 2 commits into
mainfrom
allow-aurora-to-scale
May 11, 2026
Merged

Allow aurora to scale#2110
cadmiumcat merged 2 commits into
mainfrom
allow-aurora-to-scale

Conversation

@cadmiumcat
Copy link
Copy Markdown
Contributor

@cadmiumcat cadmiumcat commented May 7, 2026

What problem does this pull request solve?

Until now we were setting the Aurora capacity in the rds module. Staging and production
had the default values (min=2ACUs max=2ACUs) which means they weren't scaling.

We want prod to be able to scale up when needed. And we want staging to be able to scale
down at quiet times.

To avoid this oversight in future, we are explicitly setting the min/max
capacity in the tfvars for each environment. Note that this sets the same
min/max for all clusters in the environment.

The minimum for prod remains at 2ACUs, which covers our current baseline usage
well and is the minimum needed for performance insights. The minimum for
stagging is now 1ACU so that it is still available, but allows for some savings.

Trello card:

Things to consider when reviewing

  • Ensure that you consider the wider context.
  • Does it work when run on your machine?
  • Is it clear what the code is doing?
  • Do the commit messages explain why the changes were made?
  • Are there all the unit tests needed?
  • Has all relevant documentation been updated?

Reminders

If you've made changes to the deployer role (files in modules/deployer-access):

  • Remember to run make <environment> forms/account apply on the relevant environments (dev, staging, user-research, and/or prod)
  • Check the #govuk-forms-deployment-notifications Slack channel to ensure the apply-forms-terraform-<environment> pipelines have run successfully

cadmiumcat added 2 commits May 7, 2026 13:49
Until now we were setting the Aurora capacity in the rds module. Staging and production
had the default values (min=2ACUs max=2ACUs) which means they weren't scaling.

We want prod to be able to scale up when needed. And we want staging to be able to scale
down at quiet times.

To avoid this oversight in future, we are explicitly setting the min/max
capacity in the tfvars for each environment. Note that this sets the same
min/max for all clusters in the environment.

The minimum for prod remains at 2ACUs, which covers our current baseline usage
well and is the minimum needed for performance insights. The minimum for
stagging is now 1ACU so that it is still available, but allows for some savings.
Rather than setting the values for min/max in the module, we pass them in for
better visibility
@cadmiumcat cadmiumcat requested review from theseanything and whi-tw May 7, 2026 13:12
Base automatically changed from remove-user-research to main May 7, 2026 14:07
@cadmiumcat cadmiumcat added this pull request to the merge queue May 11, 2026
Merged via the queue into main with commit 0c25dd1 May 11, 2026
12 checks passed
@cadmiumcat cadmiumcat deleted the allow-aurora-to-scale branch May 11, 2026 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants