API Commons · Storage · de facto

The S3 Interface

58 providers in the API Evangelist catalog claim S3 compatibility. 12 of them declare an S3 operation in a published OpenAPI. That is the denominator, and it is small — the weakest evidence base of the five standards in this programme. Shares here are coarse by construction and should be read as a signal, not a census.

116operations graded
8core tier
8extended
100vendor only
46adopters recorded

How it was measured

Graded by what adopters declare in a spec anyone can read. Live probing was tested and does not work here, and the vendor compatibility matrices this ecosystem is known for are rendered in JavaScript rather than served as text.

The core tier

What a provider has to implement before a compatibility claim means anything. Every placement is measured, and the evidence for each sits in the tier profile.

ListBucketsListObjectsDeleteBucketDeleteObjectGetObjectCreateBucketHeadObjectPutObject

Adopters

EvidenceCountWhat it means
declared12Publishes a machine-readable spec declaring them.
vendor-matrix2Publishes their own compatibility table.
prose32Says so, and publishes nothing a reader can check.

Every entry in the registry carries the URL it was read from and the date it was read. A claim is never promoted to a verdict.

Providers that reach a tier

5 of the 46 recorded adopters demonstrably reach the core tier or better.

CubeFSFilebaseOracle Cloud InfrastructureRookFastly

Artifacts

Everything this standard publishes. All of it is generated from the profile, so a re-measurement moves every artifact together.

Source

OriginatorAmazon Web Services
Read fromhttps://github.com/boto/botocore
Upstream licenceApache-2.0
Pinned ataeb03fc4ae530e0b3f47d588b6021581db870c8c
API Commonshttps://apicommons.org/standards/storage/ · https://github.com/api-commons/storage

← All standards from practice