Profile Rows
LiveBucket, object, multipart, tag, CORS, policy, delegated, and SSE-adjacent rows are grounded in the ObjectDB S3 and HTTP reference, but several remain partial because local adapters shape their behavior.
Compatibility
ObjectDB S3 Core compatibility matrix.
Compatibility matrix for the active ObjectDB s3-core-v1 gateway profile, explicit unsupported S3 families, and local adapter limits.
Current availability
Private Beta. Public beta is scheduled for .
LiveConfirm First
Matrix Snapshot
- S3 profile
- s3-core-v1
- Matrix rows
- 13
- Status values
- 6
Audience
Use this matrix when deciding whether an ObjectDB S3-shaped behavior is active in the current profile, locally bounded, explicitly unsupported, preview-only, future-facing, or still waiting on product confirmation.
Readiness Notes
Confirmation-Bound Rows
Confirm FirstCustomer credential policy, SSE backend composition, native API posture, and any broader support or operational wording need product team and documentation acceptance before promotion.
Compatibility Scope
Active Profile
This page covers ObjectDB s3-core-v1 only. Later S3 breadth needs its own profile and evidence record.
Local Adapter Boundary
Partial rows call out temporary local state, process-memory bucket configuration, payload caps, and product-bound credential behavior.
Unsupported Families
Versioning, Object Lock, lifecycle, replication, inventory, notifications, SelectObjectContent, ACLs, and website hosting remain outside this active profile.
Status Legend
Supported
Implemented and validated for the exact documented scope.
Partial
Some behavior works, but documented gaps, limits, or exclusions apply.
Unsupported
Not implemented, intentionally unavailable, or rejected at runtime.
Preview
Early surface for planning or evaluation before complete customer-facing support.
Future
Planned direction with no current runtime behavior to rely on. Check the documented status and release notes before using it.
S3 Core Matrix
| Capability | Status | Maturity | Notes |
|---|---|---|---|
| Service and bucket lifecycle | Supported | Live | ListBuckets, CreateBucket, HeadBucket, GetBucketLocation, and DeleteBucket for empty buckets are active in the s3-core-v1 gateway. |
| Object PUT, GET, HEAD, DELETE, and copy | Partial | Live | Object routes are active, but PutObject is capped at 16 MiB in the temporary local adapter and delete behavior uses local delete markers. |
| ListObjectsV2 and DeleteObjects | Partial | Live | ListObjectsV2 uses the temporary ordered-index adapter. DeleteObjects is capped at a 1 MiB body and 1,000 keys. |
| Multipart upload lifecycle | Partial | Live | CreateMultipartUpload, UploadPart, UploadPartCopy, CompleteMultipartUpload, AbortMultipartUpload, ListParts, and ListMultipartUploads are routed through temporary local multipart state. |
| Object tags and user metadata | Partial | Live | Object tagging routes and user metadata are active with local adapter caps: 10 tags, 128-byte tag keys, 256-byte values, and 2 KiB aggregate metadata budgets. |
| Bucket CORS and preflight | Partial | Live | PutBucketCors, GetBucketCors, DeleteBucketCors, and OPTIONS preflight are active through process-memory local bucket configuration capped at 64 KiB and 100 rules. |
| Bucket policy | Partial | Confirm First | PutBucketPolicy, GetBucketPolicy, and DeleteBucketPolicy are active through local bucket-policy state capped at 20 KiB. Customer credential and policy composition remains product-bound. |
| SSE request headers and encryption identity | Partial | Confirm First | SSE headers are validated and mapped into ObjectDB encryption identity. Encryption-at-rest backend composition remains a separate status-note path. |
| Presigned requests and delegated browser POST | Partial | Confirm First | SigV4 and delegated checks are source-backed for the local gateway. Browser POST uses the PutObject local cap plus a 64 KiB form envelope. |
| Versioning, Object Lock, lifecycle, replication, inventory, notifications, SelectObjectContent, ACLs, and website hosting | Unsupported | Confirm First | These advanced S3 families are outside the active s3-core-v1 profile and return explicit NotImplemented responses. |
| Customer credential and authorization parity | Confirm First | Confirm First | The local gateway derives development principals and operation permissions from ObjectDB-specific headers while broader customer credential composition matures. |
| Native ObjectDB object versions, manifests, policies, placement, and events | Preview | Preview | Native object-platform language stays in preview-contract territory until public references and accepted evidence land. |
| Additional S3 compatibility profile families | Future | Future | Later S3 profile breadth is roadmap direction only. The current page documents s3-core-v1. |
Local Adapter Limits
| Limit | Value | Applies to |
|---|---|---|
| Request target | 8192 bytes | S3 route classification |
| Aggregate headers | 32768 bytes | S3 route classification |
| Query parameters | 64 parameters | Query-shape routing |
| Body chunk buffer | 65536 bytes | Streaming body reads |
| Concurrent S3 requests | 1024 requests | Gateway ingress |
| Slow client timeout | 30 seconds | Request startup and body progress |
| PutObject local payload | 16 MiB | Temporary local object adapter |
| DeleteObjects body | 1 MiB | Temporary local batch delete adapter |
| DeleteObjects keys | 1000 keys | Temporary local batch delete adapter |
| Object tags | 10 tags, 128-byte keys, 256-byte values, 2 KiB total | Temporary local tag adapter |
| User metadata | 128-byte keys, 2 KiB values, 2 KiB total | Temporary local metadata adapter |
| Bucket CORS | 64 KiB body and 100 rules | Temporary local CORS adapter |
| Bucket policy | 20 KiB document | Temporary local bucket-policy adapter |
Explicit Exclusions
Requests for versioning, Object Lock, lifecycle, replication, inventory, notifications, SelectObjectContent, ACLs, and website hosting are outside the active profile and should return S3-shaped NotImplemented responses.
Source scope
| Matrix area | Source scope | Status | Last reviewed |
|---|---|---|---|
| S3 profile rows | documented source scope | Source-scoped | 2026-08-16 |
| Quickstart-supported workflow | documented source scope and /products/objectdb/quickstart/ | Source-scoped | 2026-08-16 |
| HTTP route shape and limits | documented source scope and /products/objectdb/reference/http/ | Source-scoped | 2026-08-16 |
| Compatibility page artifact | documented source scope and docs/compatibility/documented source scope-objectdb-s3-core-compatibility.md | Source-scoped | 2026-08-16 |
Internal public documentation boundaries track this ObjectDB compatibility matrix and the review note required to change row status.
Limits
This matrix covers ObjectDB s3-core-v1 only. Do not use it to expand advanced S3 family claims, customer credential commitments, or operational outcomes beyond the cited evidence.
See the S3 and HTTP reference for route shapes and the ObjectDB limits and compatibility guidance for review status.
Safe Next Steps
Available
Run the ObjectDB quickstartExercise bucket create, object put/get, ListObjectsV2, cleanup, and explicit unsupported-surface behavior locally.
Available
Read S3 and HTTP referenceUse route shapes, errors, response headers, and local adapter constraints behind each matrix row.
Available
Review ObjectDB limitsCheck source records before expanding ObjectDB compatibility, credential, support, or operational wording.
Available
Read known limitsSee unsupported S3 family behavior, local adapter constraints, and product-bound claim areas.
Available
Compare compatibility modelUse the workflow for stale-row checks, status-note refresh, owner review, and release-note updates.
