[Issue 965] Configure RDS to pass Security Hub checks #1048
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.
Summary
Fixes #965
Time to review: 10 mins
Changes proposed
postgres
to a randomized username of the formrootd475cc8eefda848e49bff38b509233ff
.prod
to 2 (one writer, one reader).Context for reviewers
This addresses the issues found by Security Hub.
The requirement "RDS DB clusters should be configured for multiple Availability Zones" has a cost implication as Aurora Serverless reader instances run continuously at the minimum configured scale. Therefore we only set 2 instances in the
prod
environment (1 writer and 2 reader), and leave the other environments with only 1 instance (a writer).Warning
Since this changes the database superuser username, it forces a replacement of the RDS clusters. All data would be lost. After the clusters have been recreated, we will need to re-run the role manager lambda to create other users, so that the API can connect.
Partial terraform plan:
Additional information
N/A