My AWS Batch job service uses a lot of space to S3, while my code doesn't work with S3?

I have 5 Batch jobs running on AWS Batch with Fargate, when it was running I noticed the capacity to S3 spiked through the NAT Gateway. I queried VPC Logs using Athena and found that the destination IP is of S3 None of my code uses S3, when I turn them off the capacity going to S3 is completely reduced. I don't understand why my Batch job service uses S3 while my code doesn't. Is there any way to investigate to know exactly where the capacity is coming from? (except https://aws.amazon.com/premiumsupport/knowledge-center/vpc-find-traffic-sources-nat-gateway/?nc1=h_ls , I read it). I understand it is possible to use S3 VPC Endpoint to handle throughput through the NAT Gateway, but I want to find the root cause.