mirror of
https://github.com/databasus/databasus.git
synced 2026-04-06 00:32:03 +02:00
S3 storage connects successfully but backup fails to save when Object Lock is enabled #311
Assignees
MrUnknownDE
Clear assignees
MrUnknownDE
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github/databasus#311
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @smyoss on 12/29/2025
After successfully connecting and saving a new S3 storage configuration, backup operations fail and do not actually save to the bucket. While the initial storage mapping now completes without error, attempting to create a backup results in a failure during the upload phase. This appears related to the same underlying issue with Object Lock requirements—the PutObject request during backup lacks the required Content-MD5 or x-amz-checksum-* headers. Users can configure the storage but cannot use it for its intended purpose.
Technical Details
Storage connection: Now succeeds (previously failed with same error)
Backup operation: Fails during upload/save
Suspected error: Content-MD5 OR x-amz-checksum- HTTP header is required for Put Object requests with Object Lock parameters
Environment: S3 bucket with Object Lock enabled
Symptom: Storage saves successfully, but backups do not persist to S3
Root cause: PutObject requests during backup likely still missing required headers (Content-MD5 or x-amz-checksum-*) when Object Lock parameters are present
Error Message
Backup error details
save to storage: failed to upload part 1: ContentMD5 OR x-amz-checksum-HTTP header is required for Put Part requests with Object Lock parameters
Version
v2.18.3
Thank you so much for your help!