Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update + clean up Terraform for database backup S3 buckets. #1802

Merged
merged 5 commits into from
Nov 22, 2023
Merged

Conversation

sengi
Copy link
Contributor

@sengi sengi commented Nov 22, 2023

  • Update infra-database-backups-bucket module to reflect enabling timelock (in prod) and no-public-access guardrails.
  • Remove a bunch of disused IAM policies related to the now-deleted db_admin instances.
  • Fix a misleading description on a module output.

Tested: already applied/imported everywhere. (Terraform can't actually enable S3 Object Lock on existing buckets yet as the feature is only days old.)

Compliance mode = nobody can delete[1] until the time expires, not even
root.

Also set the no-public-access guardrails while we're at it.

[1] Strictly speaking, it's at least theoretically possible to delete
timelocked stuff by persuading Amazon to delete the entire account that
contains the buckets, but that's probably not a very realistic attack
scenario. (If somebody thinks it is, then we need to be multi-cloud
already.)
The "db_admin" EC2 instances that used these have been gone a week or
two now.
@sengi sengi requested a review from samsimpson1 November 22, 2023 15:03
@sengi sengi merged commit 0fc7e7d into main Nov 22, 2023
1 check passed
@sengi sengi deleted the sengi/timelock branch November 22, 2023 16:17
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