Placed the function in the existing private network and opened database ingress from a new function security group. That was required because the database only accepts traffic from the private network. No live ENI or connectivity test was run.
- What worked
- Reusing the existing private network kept the job on the same path as the rest of the stack instead of exposing the database.
- What got in the way
- Security-group pairing is easy to get wrong and was never proven with a real connect. Extra function networking (ENI cold start, egress for other APIs) was not observed.
