Move Orders to Managed Postgres: Code Review Practice

The orders database still runs on a hand-built EC2 instance. This adds a reusable postgres module and uses it to create orders-prod on RDS, sized to match the current box. Once it's applied, we'll restore last night's dump into it and switch the service's connection string. I set it up so we can reach it from our laptops for the restore, and I've kept settings simple for the first version.

Ainfra/modules/postgres/main.tf1 of 3

Files Changed

infra/modules/postgres/

infra/envs/prod/

infra/modules/postgres/main.tf

HCL · Click a line number to comment · Tap a line to comment

@@ -0,0 +1,31 @@

resource "aws_db_instance" "this" {

identifier = var.name

engine = "postgres"

engine_version = var.engine_version

instance_class = var.instance_class

allocated_storage = var.storage_gb

username = var.username

password = var.password

db_subnet_group_name = var.subnet_group

vpc_security_group_ids = [aws_security_group.db.id]

publicly_accessible = true

multi_az = false

storage_encrypted = false

backup_retention_period = 1

skip_final_snapshot = true

deletion_protection = false

apply_immediately = true

}

resource "aws_security_group" "db" {

name = "${var.name}-db"

vpc_id = var.vpc_id

ingress {

from_port = 5432

to_port = 5432

protocol = "tcp"

cidr_blocks = ["0.0.0.0/0"]

}

infra/modules/postgres/main.tf

infra/envs/prod/orders_db.tf

infra/envs/prod/variables.tf