- Newest
- Most votes
- Most comments
Hello,
Thank you for contacting AWS Re:Post. For the Version ID error, there are different solutions. You can refer the document below:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/inventory-configure-bops.html
Please let us know if there are further questions.
I encountered this error in a bucket that doesn't have versioning enabled, which had me confused initially since the official documentation for this error seems to assume that you do.
In my case, the issue seems to have arisen from having selected "Include all versions" under "Inventory scope" when I created the inventory configuration used to generate the manifest.json (and CSV) file used when creating the batch operations job, e.g.:
Making this selection on a non-versioned bucket seems to result in the VersionId field of the CSV file being left blank, which causes the issues.
Relevant content
- asked 3 years ago
- asked 3 years ago
- asked 3 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
It blows my mind that we are using a built in S3 function for inventory and job from inventory, then it fails because of something like this. Then there is an entire document for performing an ETL on your inventory files, INSTEAD OF JUST FIXING THE PROBLEM WITH THE SERVICE. Just handle the case when there are missing version ids!