From 19902ee6576cb623cdae64f217f0311048d7935a Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Sat, 24 Oct 2026 14:50:21 +0100 Subject: [PATCH] serve s3: document that x-amz-expected-bucket-owner is ignored See #10082 --- cmd/serve/s3/serve_s3.md | 1 + 1 file changed, 1 insertion(+) diff --git a/cmd/serve/s3/serve_s3.md b/cmd/serve/s3/serve_s3.md index c0155aa44..3537f9261 100644 --- a/cmd/serve/s3/serve_s3.md +++ b/cmd/serve/s3/serve_s3.md @@ -539,6 +539,7 @@ ignored. | Checksums | Partial | The `x-amz-checksum-*` of a `PutObject` (CRC32, CRC32C, CRC64NVME, SHA1 or SHA256) is checked and returned with the metadata. The checksums of multipart uploads aren't supported. | | `GetObjectAttributes` | Partial | Everything but the checksums of multipart uploads. | | Object tagging | Partial | `GetObjectTagging`, `PutObjectTagging` and `DeleteObjectTagging` work, but tags are kept in memory with the metadata. | +| Bucket owner | No | `serve s3` has no AWS account IDs, so `x-amz-expected-bucket-owner` and `x-amz-source-expected-bucket-owner` are ignored. | | ACLs | Partial | `GetBucketAcl` and `GetObjectAcl` give the owner full control. Only the `private` ACL can be set. | | CORS | Partial | Preflight (`OPTIONS`) requests are answered, allowing any origin. CORS configuration (`PutBucketCors`) isn't supported. | | Server side encryption | No | SSE-S3 (`AES256`) is accepted but the data isn't encrypted. SSE-KMS and SSE-C are refused. |