S3 API Compatibility

This page documents S3 APIs supported by MinIO Object Storage. For reference documentation on any given API, see the corresponding documentation for Amazon S3.

Object APIs

• CopyObject
• DeleteObject
• DeleteObjects
  • Conditional DELETE: published Server 20260903 ignores If-Match. Current main supports nonempty If-Match on single DeleteObject (#145/#178), including addressed-version comparison. Batch DeleteObjects still ignores <Object><ETag> and provides no per-item conditional guard. See scope and limitations.
• DeleteObjectTagging
• GetObject
• GetObjectAttributes
• GetObjectTagging
• HeadObject
• ListObjects
• ListObjectsV2
• ListObjectVersions
• PutObject
• PutObjectTagging
• RestoreObject
• SelectObjectContent

Object Locking

• GetObjectRetention
• PutObjectRetention
• GetObjectLegalHold
• PutObjectLegalHold
• GetObjectLockConfiguration
• PutObjectLockConfiguration

Unsupported API Object Endpoints

GetObjectAcl
PutObjectAcl

Multipart Uploads

• AbortMultipartUpload
• CompleteMultipartUpload
• CreateMultipartUpload
• ListMultipartUploads
• ListParts
• UploadPart
• UploadPartCopy

Differences from S3 APIs for Multipart Uploads

• Published Server 20260903 treats a non-empty ListMultipartUploads prefix as an exact object name. An empty prefix uses node-local volatile state without complete pagination, marker or delimiter semantics.
• PR #198 adds durable discovery, global pagination and continuation after a native marker upload is deleted. The pre-release compatibility follow-up defaults to legacy, retaining the old limitations; strict mode requires an explicit MINIO_API_MULTIPART_LISTING=strict environment setting. Before enabling strict mode, upgrade all writers, drain legacy uploads and validate both the read-only preflight and scan capacity. Strict mode returns 503 for insufficient coverage, legacy records or resource limits. An ordinary upgrade requires neither a mode switch nor forced upload drain. See the implementation and upgrade contract for ordering, scan capacity and the cancellation boundary for delayed creation writes. This is not a release or production-acceptance claim.
• The AbortIncompleteMultipartUpload lifecycle action is not supported with PutBucketLifecycle.

Bucket APIs

• CreateBucket
• DeleteBucket
• DeleteBucketEncryption
• DeleteBucketTagging
• GetBucketEncryption
• GetBucketLocation
• GetBucketTagging
• GetBucketVersioning
• HeadBucket
• ListBuckets
• ListDirectoryBuckets
• PutBucketEncryption
• PutBucketTagging
• PutBucketVersioning

Bucket Replication

• GetBucketReplication
• PutBucketReplication
• DeleteBucketReplication

Bucket Lifecycle

• GetBucketLifecycle
• GetBucketLifecycleConfiguration
• PutBucketLifecycle
• PutBucketLifecycleConfiguration
• DeleteBucketLifecycle

Bucket Notifications

• GetBucketNotification
• GetBucketNotificationConfiguration
• PutBucketNotification
• PutBucketNotificationConfiguration

Bucket Policies

• GetBucketPolicy
• GetBucketPolicyStatus
• PutBucketPolicy
• DeleteBucketPolicy
• GetBucketCors
• PutBucketCors
• DeleteBucketCors

Unsupported API Bucket Operations

GetBucketInventoryConfiguration
PutBucketInventoryConfiguration
DeleteBucketInventoryConfiguration
GetBucketMetricsConfiguration
PutBucketMetricsConfiguration
DeleteBucketMetricsConfiguration
PutBucketWebsite
GetBucketLogging
PutBucketLogging
PutBucketAccelerateConfiguration
DeleteBucketAccelerateConfiguration
PutBucketRequestPayment
DeleteBucketRequestPayment
PutBucketAcl
HeadBucketAcl
GetPublicAccessBlock
PutPublicAccessBlock
DeletePublicAccessBlock
GetBucketOwnershipControls
PutBucketOwnershipControls
DeleteBucketOwnershipControls
GetBucketIntelligentTieringConfiguration
PutBucketIntelligentTieringConfiguration
ListBucketIntelligentTieringConfigurations
DeleteBucketIntelligentTieringConfiguration
GetBucketAnalyticsConfiguration
PutBucketAnalyticsConfiguration
ListBucketAnalyticsConfigurations
DeleteBucketAnalyticsConfiguration
CreateSession

MinIO alternatives for unsupported Bucket resources

• For calls to BucketACL or ObjectACL operations, use Policies.
• BucketCORS operations are supported since RELEASE.2026-09-03T13-18-01Z. A bucket with its own CORS configuration is served only by that configuration; buckets without one use the server-wide MINIO_API_CORS_ALLOW_ORIGIN policy, which allows every origin by default.
• For calls to BucketWebsite operations, use caddy or nginx.
• For calls to BucketAnalytics, BucketMetrics, or BucketLogging operations, use Bucket Notifications.