Building Database Using Terraform in AWS for Maximal Isolation Usability
summary
Provides a concrete Terraform pattern that builds isolated DB accounts and VPCs on AWS, wires apps to databases via PrivateLink with endpoint services, and automates RDS IP churn using a Lambda that updates load‑balancer targets. Shows pitfalls: bundled AMIs create unmanaged EBS disks, so use thin AMIs plus Ansible; prefer SessionManager instead of bastions; manage secrets in Parameter Store/Secrets Manager; use Route53 private zones for consistent FQDNs; recommend EFS for backup restores and template‑driven, versioned Terraform modules.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:14VPCs vs Accounts vs Subnets
- 7:30Planning for Cattle vs Pets
- 13:32Network Planning, & thoughts around it
- 20:21RDS LB Update Lambda Flow
- 20:57Doing DNS right and early!
- 25:57DNS as a Diagram
- 27:24Password and Secret Management
- 36:51Putting it together
related talks
25mSecuring and Scaling AWS with Terraform, Vault, and Veeam: A Practical Guide
30mTerraforming RDS: What Instacart has learned managing over 50 AWS RDS Postgres instances with Terr
10mInfrastructure as a Code Best Practices with Terraform
30mTerraform in Depth QA and Fireside Chat
55mBest practices
30mTerraform Practices to Enable Infrastructure Scaling
41mTerraform Practices - The Good, the Bad, and the Ugly
30mBuilding Datalakes for an International Bank with HashiCorp Terraform