Skip to content
Zenko CloudServer, an open-source Node.js implementation of the Amazon S3 protocol on the front-end and backend storage capabilities to multiple clouds, including Azure and Google.
Branch: development/8.1
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin bugfix: ZENKO-315 Update create NFS bucket script Jul 9, 2018
conf bf: ZENKO-835 do not replicate lifecycle actions Jul 28, 2018
docs bugfix: S3C-1922_Remove_scality/s3server_refs Feb 6, 2019
eve bf(ZENKO-1511): Update Ceph CI Image Mar 1, 2019
lib Merge branch 'bugfix/ZENKO-1568-lc-update-crash' into q/8.1 Mar 15, 2019
.eslintrc improvement: ZENKO-1421 ignore new rules for now Jan 7, 2019
.gitignore improvement: ignore .tox dir Nov 15, 2018 Add Contribution rules Jun 8, 2016
DockerfileMem ft: add stats to healthcheck route Nov 22, 2016
LICENSE Update LICENSE Feb 25, 2017
config.json Merge remote-tracking branch 'origin/w/8.0/feature/S3C-1807-MD-admin-… Nov 15, 2018
dataserver.js feat(ZENKO-1270): pfs daemon Nov 15, 2018
locationConfig.json bf: ZENKO-745 unique location metrics redis keys Jul 21, 2018
mdserver.js ZENKO-140 - rf: move metadata backends to Arsenal Mar 7, 2018
package-lock.json Merge remote-tracking branch 'origin/w/8.0/feature/S3C-2032/update-ar… Mar 15, 2019

Zenko CloudServer

Zenko CloudServer logo

CircleCI Scality CI Docker Pulls Docker Pulls


CloudServer (formerly S3 Server) is an open-source Amazon S3-compatible object storage server that is part of Zenko, Scality’s Open Source Multi-Cloud Data Controller.

CloudServer provides a single AWS S3 API interface to access multiple backend data storage both on-premise or public in the cloud.

CloudServer is useful for Developers, either to run as part of a continous integration test environment to emulate the AWS S3 service locally or as an abstraction layer to develop object storage enabled application on the go.

Learn more at

May I offer you some lovely documentation?


Run your Zenko CloudServer with Docker


In order to contribute, please follow the Contributing Guidelines.



Building and running the Zenko CloudServer requires node.js 6.9.5 and npm v3 . Up-to-date versions can be found at Nodesource.

Clone source code

git clone

Install js dependencies

Go to the ./S3 folder,

npm install

If you get an error regarding installation of the diskUsage module, please install g++.

If you get an error regarding level-down bindings, try clearing your npm cache:

npm cache clear

Run it with a file backend

npm start

This starts a Zenko CloudServer on port 8000. Two additional ports 9990 and 9991 are also open locally for internal transfer of metadata and data, respectively.

The default access key is accessKey1 with a secret key of verySecretKey1.

By default the metadata files will be saved in the localMetadata directory and the data files will be saved in the localData directory within the ./S3 directory on your machine. These directories have been pre-created within the repository. If you would like to save the data or metadata in different locations of your choice, you must specify them with absolute paths. So, when starting the server:

mkdir -m 700 $(pwd)/myFavoriteDataPath
mkdir -m 700 $(pwd)/myFavoriteMetadataPath
export S3DATAPATH="$(pwd)/myFavoriteDataPath"
export S3METADATAPATH="$(pwd)/myFavoriteMetadataPath"
npm start

Run it with multiple data backends

export S3DATA='multiple'
npm start

This starts a Zenko CloudServer on port 8000. The default access key is accessKey1 with a secret key of verySecretKey1.

With multiple backends, you have the ability to choose where each object will be saved by setting the following header with a locationConstraint on a PUT request:


If no header is sent with a PUT object request, the location constraint of the bucket will determine where the data is saved. If the bucket has no location constraint, the endpoint of the PUT request will be used to determine location.

See the Configuration section in our documentation here to learn how to set location constraints.

Run it with an in-memory backend

npm run mem_backend

This starts a Zenko CloudServer on port 8000. The default access key is accessKey1 with a secret key of verySecretKey1.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.