Allow aurora to scale#2110
Merged
Merged
Conversation
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
whi-tw
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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
Reminders
If you've made changes to the deployer role (files in
modules/deployer-access):make <environment> forms/account applyon the relevant environments (dev,staging,user-research, and/orprod)apply-forms-terraform-<environment>pipelines have run successfully