Skip to content

Commit

Permalink
Merge pull request #1449 from Neon-White/docs-s3-comp
Browse files Browse the repository at this point in the history
Docs | S3 Compatibility
  • Loading branch information
Neon-White authored Dec 2, 2024
2 parents d87725a + 9300322 commit 2bca4d8
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions doc/s3-compatibility.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
[NooBaa Operator](../README.md) /

# S3 Compatibility in NooBaa
S3 (also known as Simple Storage Service) is an object storage service provided by Amazon. However, S3 is often colloquially used to refer to the S3 API - the RESTful interface for interaction with AWS S3. Over time, the S3 API has reached a point where many consider it the de facto standard API for object storage, and is supported by many cloud providers and storage vendors - even ones like Microsoft Azure and Google Cloud Platform, which also offer their own APIs alongside S3 compatibility.

## API Compatibility
Due to the wide adoption of the S3 API, NooBaa has been designed to be S3 compatible and adherent. NooBaa buckets and objects can be managed with most S3 clients without a need for proprietary tools or workarounds. All a user needs in order to interact with NooBaa through an S3 client is the S3 endpoint of the NooBaa system, and a set of fitting credentials.
The endpoint can be found by checking the `routes` and `services` on a cluster, and the default admin credentials can be found in the same namespace that NooBaa was installed in, inside the `noobaa-admin` secret.
For further reference of supported API calls in NooBaa, you can check out [AWS API Compatibility](https://github.com/noobaa/noobaa-core/blob/master/docs/design/AWS_API_Compatibility.md)

## Utilization of S3 Compatible Storage Services
NooBaa can also be used as a gateway to other storage services that are S3 compatible. This means that NooBaa can be used to store and manage data in certain storage services (as long as they provide an S3 compatible API), even if they are not natively supported by the product. This is done by creating a [backingstore](backing-store-crd.md) or [namespacestore](namespace-store-crd.md) of type `s3-compatible` and providing the the appropriate endpoint.

0 comments on commit 2bca4d8

Please sign in to comment.