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.
Alternatives To Cloudserver
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Free For Dev70,220
13 hours ago19HTML
A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
6 days ago155agpl-3.0Jinja
Set up a personal VPN in the cloud
Boto38,10011,5454,6804 days ago1,140July 06, 2022172apache-2.0Python
AWS SDK for Python
23 days ago2October 09, 201784mitMako
Amazon EC2 instance comparison site
Amplify Cli2,71014494 days ago631September 19, 2022644apache-2.0TypeScript
The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.
Mrjob2,58411218 months ago62September 17, 2020211otherPython
Run MapReduce jobs on Hadoop or Amazon Web Services
Mc2,462151519 hours ago50April 22, 202137agpl-3.0Go
Simple | Fast tool to manage MinIO clusters :cloud:
2 months ago102apache-2.0Groovy
[Asgard is deprecated at Netflix. We use Spinnaker ( ).] Web interface for application deployments and cloud management in Amazon Web Services (AWS). Binary download:
Bank Vaults1,85616a day ago71April 05, 2022230apache-2.0Go
A Vault swiss-army knife: a K8s operator, Go client with automatic token renewal, automatic configuration, multiple unseal options and more. A CLI tool to init, unseal and configure Vault (auth methods, secret engines). Direct secret injection into Pods.
List Of Python Api Wrappers1,769
2 years ago8
List of Python API Wrappers and Libraries
Alternatives To Cloudserver
Select To Compare

Alternative Project Comparisons

Zenko CloudServer

Zenko CloudServer logo

Docker Pulls Docker Pulls


CloudServer (formerly S3 Server) is an open-source Amazon S3-compatible object storage server that is part of Zenko, Scalitys 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 10.x and yarn v1.17.x . Up-to-date versions can be found at Nodesource.

Clone source code

git clone

Install js dependencies

Go to the ./S3 folder,

yarn install --frozen-lockfile

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 yarn cache:

yarn cache clean

Run it with a file backend

yarn 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"
yarn start

Run it with multiple data backends

export S3DATA='multiple'
yarn 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

yarn run mem_backend

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

Run it with Vault user management

Note: Vault is proprietary and must be accessed separately.

export S3VAULT=vault
yarn start

This starts a Zenko CloudServer using Vault for user management.

Popular Cloud Computing Projects
Popular Amazon Projects
Popular Cloud Computing Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
Aws S3
Cloud Native
Cloud Storage
Object Storage
S3 Storage