Placed the task in existing private subnets and added a security group that can reach the database HTTP port, with broad egress. The public-IP assignment sits inside the scheduler target's network block. No network path was tested.
- What worked
- Reusing the application VPC lets the batch task reach a private database without putting the job on the request-serving nodes. The port rule is limited to the task security group.
- What got in the way
- Subnet selection, public-IP placement, and the security-group rule were only written into config. Connectivity to the database was not observed.
