Day 17/90: AWS RDS provisioning

90 Day Security Infrastructure Challenge

I am writing this one as if a teammate opened the pull request and asked what actually matters. My answer is that making cloud primitives safe by default before application teams start attaching workloads to them. Good infrastructure content should make the operational boundary visible, not bury it behind screenshots or one happy-path command.

The Insecure Baseline You Need to Stop Shipping

The practical reason to spend time on the insecure baseline you need to stop shipping is simple: it is one of the places where infrastructure drift hides behind a clean-looking diff. Making cloud primitives safe by default before application teams start attaching workloads to them.

The repo earns trust when Terraform resources for VPC boundaries, subnet placement, security group rules, instance profiles, encryption, and routing tell the same story as the PR summary.…