s3 batch operations takes to long

Hi There

Take a look at this previous answer

https://repost.aws/questions/QUzH_mXBObTuO9iq_pvJkkoA/s-3-batch-operations-job-stays-active

A batch job performs a specified operation on every object that is included in its manifest. A manifest lists the objects that you want a batch job to process and it is stored as an object in a bucket. After you create a job, Amazon S3 processes the list of objects in the manifest and runs the specified operation against each object.

When a S3 batch job is "active" it means Amazon S3 is performing the requested operation on the objects listed in the manifest. While a job is Active, you can monitor its progress using the Amazon S3 console or the DescribeJob operation through the REST API, AWS CLI, or AWS SDKs.

The performance/speed of any particular Batch Operations job will depend on a variety of factors, including :

• The number of objects in the manifest
• The type of operation (Glacier restore, copy, Lambda function, etc)
• The number of active jobs your account
• The number of enqueued jobs for your account
• Other traffic to the source and/or destination bucket
• The size of the objects

You can refer to the following link for information on troubleshooting S3 batch jobs: https://aws.amazon.com/premiumsupport/knowledge-center/s3-troubleshoot-batch-operations/

If you need additional support, then you can also open a case with AWS Premium Support to review the details of this particular job.