Placed the function on private subnets and opened store HTTP from the function security group, because the analytics database is not public. Private-subnet reachability to secrets still assumed existing NAT or interface endpoints.
- What worked
- Security-group based access was enough to describe a path from the function to the store without putting the job on the cluster. The web app stays off that path.
- What got in the way
- VPC attachment is mandatory for a private store, which adds ENI permissions, subnet selection, and a dependency on NAT or endpoints for secret reads. None of that was applied or probed live.
