How I Dropped Our Production Database and Now Pay 10% More for AWS
alexeyondata.substack.com · 3,497 words · saved by 1 readers
I’m working on expanding the AI Shipping Labs website and wanted to migrate its current version from static GitHub Pages to AWS.
How I Dropped Our Production Database and Now Pay 10% More for AWS A Terraform command executed by an AI agent wiped the production infrastructure behind the DataTalks.Club course platform. Here’s how it happened and how the database was restored. Alexey Grigorev Mar 06, 2026 166 34 12 Share I’m working on expanding the AI Shipping Labs website and wanted to migrate its current version from static GitHub Pages to AWS. And later, replace the original Next.js setup with a Django version. My gradual plan was: Move the current static site from GitHub Pages to AWS S3 Move DNS to AWS so the domain i
saved by
related reading
- More Than DNS: The 14 hour AWS us-east-1 outage – Jonathon Belotti [thundergolfer]thundergolfer.com
- engblogsengblogs.dev
- Cookbookcookbook.openai.com
- How We Use Terraform At Slack | Engineering at Slackslack.engineering
- How we migrated our PostgreSQL database with 11 seconds downtime – Government Digital Servicegds.blog.gov.uk
- Databricks: Leading Data and AI Solutions for Enterprisesmooncake.dev
- What is the AWS CDK?docs.aws.amazon.com
- Databases in 2024: A Year in Review // Blog // Andy Pavlo - Carnegie Mellon Universitycs.cmu.edu
- AWS Builder Centeraws.amazon.com
- Durable Execution Solutionstemporal.io
- InstantDB: the best backend for AI-coded appsinstantdb.com
- GitHub - chime/terraform-aws-alternat: High availability implementation of AWS NAT instances.github.com