Troubleshooting Batch Operations
The following topics cover common errors to help you troubleshoot issues that you might encounter while working with Amazon S3 Batch Operations.
To troubleshoot issues with S3 Batch Replication, see Batch Replication errors.
There are two primary types of failures that result in Batch operation errors:
-
API Failure – The requested API (such as
CreateJob) has failed to execute. -
Job Failure – The initial API request succeeded but the job failed, for example, due to issues with the manifest or permissions to objects specified in the manifest.
NoSuchJobException
Type: API failure
This can occur if the job has expired, or when the ID used in the CreateJob request isn't the same one used in the DescribeJob or UpdateJobStatus request.
Jobs expire after 90 days in a terminal state (Complete, Cancelled, or Failed) For more information, see Tracking job status and completion reports.
Related error messages
No such job
Recommended actions
To troubleshoot NoSuchJobException you can try the following:
-
Verify that the job exists and is in your account. You can use the following Amazon CLI command:
aws s3control list-jobs --account-id 111122223333 -
Verify that the ID received in the
CreateJobrequest is the same one used in theDescribeJoborUpdateJobStatusrequest.
AccessDeniedException
Type: API failure
The AccessDeniedException occurs when an S3 Batch Operations request is blocked because of unsupported operations or the IAM identity making the request doesn't have sufficient permissions to perform an action.
Related error messages
Access Denied
Recommended actions
To troubleshoot AccessDeniedException you can try the following:
-
Make sure that S3 Batch Operations supports the operation or feature in the Region. For a list of supported operations, see Operations supported by S3 Batch Operations. Batch operations are supported for General purpose buckets in all Regions, but operations for Directory buckets are only available in Regional and Zonal endpoints for directory buckets.
-
Make sure the IAM identity making the request has permissions to create and manage batch operations, for a list of permissions, see Granting permissions for Batch Operations.
SlowDownError
Type: API failure
The SlowDownError exception occurs when your account has exceeded the request rate limit for S3 Batch Operations.
Recommended actions
To resolve SlowDownError exceptions you can try the following:
-
Slow down the request rate and retry. For more information, see Retry with backoff pattern in the Amazon Prescriptive Guidance.
InvalidManifestContent
Type: Job failure
The InvalidManifestContent exception occurs when there are issues with the manifest file format, or issues with the content that S3 Batch Operations uses to process objects.
Related error messages
-
Required fields are missing in the schema: + missingFields -
Invalid Manifest Content -
The S3 Batch Operations job failed because it contains more keys than the maximum allowed in a single job. Please split the job into multiple smaller jobs or reach out to customer support for next steps.
Recommended actions
To troubleshoot InvalidManifestContent you can try the following:
For manifest format issues:
-
Ensure that the manifest follows the required format specifications. All required columns should be present, properly formatted and consistent across the manifest. For examples, see Specifying a manifest.
For content issues:
-
Replace special characters in object keys with their XML entity codes and ensure that object keys meet the Amazon S3 naming conventions. For more information, see Naming Amazon S3 objects.
-
Ensure all object keys are URL encoded.
-
Break large jobs into smaller jobs. You can see how many objects are supported for each operation Operations supported by S3 Batch Operations.