Ceph offers what is called RADOS Gateway (or RGW).

S3 at 45Dives ClusteringĪt 45 Drives, we use Ceph for our clustered storage solutions, which has its underlying architecture built on object storage. This means that each request from the client has to contain all the information necessary to understand the request, and doesn’t have the ability to take advantage of any stored context on the server-side – the client is responsible for handling application state information. The REST API is considered a “stateless” protocol, where the server does not store any state about the client sessions on its side. It’s an API that uses HTTP requests to get, put, post and delete data. S3 is what is considered an HTTP REST API. The goal of this blog is to outline some of the most common implementations of the S3 protocol. The level of complexity for these solutions vary from basic CRUD (create, remove, update, delete) functions, to full S3 Compatibility. While it’s true that the S3 API (Application Programming Interface) is developed and released by Amazon, it has implementations within a wide variety of storage systems. One example is how Ceph implements it via its RADOS Gateways (RGW).

S3 is used for interfacing with object storage over a network, by using buckets, keys, and operations. However, the S3 protocol is actually used in many places outside of AWS. When most people use S3 (Simple Storage Service), the first thing they think about is Amazon Cloud Storage.

Cyberduck connect to s3