Delete Objects and Errors

Delete objects safely and diagnose standard XML errors returned by the S3 endpoint.

Delete an object

Use DeleteObject with the exact bucket and key. S3 deletion is idempotent and returns success even when the object is already absent.

AWS CLI
aws s3api delete-object \
  --bucket <bucket> \
  --key media/old-video.mp4 \
  --endpoint-url https://storage.acdn.uz \
  --profile acdn

Deletion behavior

  • DeleteObject targets one object key. Recursive directory deletion is not an S3 object operation.
  • Use individual DeleteObject requests; the DeleteObjects batch operation is not implemented.
  • After a successful delete, the object is removed from browse listings and subsequent reads return NoSuchKey.
  • Physical copies are retained for three days and then removed by the daily purge process.

S3 error responses

Signed S3 requests always receive an XML error document with Code, Message, Resource, and RequestId. Common errors include:

SignatureDoesNotMatch

The endpoint, region, canonical path, payload hash, or signed headers differ from the request.

AccessDenied

The credential is not allowed to access the requested bucket or operation.

NoSuchKey / NoSuchUpload

The object or multipart upload ID does not exist.

InvalidPart / InvalidPartOrder

Multipart completion references missing, mismatched, or incorrectly ordered parts.

EntityTooSmall

A non-final multipart part is smaller than 5 MiB.

NotImplemented

The requested S3 bucket or batch operation is outside the supported matrix.