Placed the function on private subnets and added security-group ingress so it can reach the private database HTTP port. This was required because the database is not public. No live network test was run.
- What worked
- Existing private-subnet and security-group patterns extended naturally: one new ingress rule from the function security group was enough on paper.
- What got in the way
- Database access is currently limited to the compute cluster security group, so forgetting the new ingress rule would silently block the job. VPC-attached functions also complicate first-run debugging.
