S3rver

S3rver is a lightweight server that responds to some of the same calls Amazon S3 responds to. It is extremely useful for testing S3 in a sandbox environment without actually making calls to Amazon.

The goal of S3rver is to minimise runtime dependencies and be more of a development tool to test S3 calls in your code rather than a production server looking to duplicate S3 functionality.

This Fork

This fork has the following differences:

Can upload multipart files (Initiate and complete supported. As well as PUT part)
Can add listeners for ObjectCreated and ObjectDeleted
- I'm using it for doing local lambda events
Can add your own server http listeners to the app
- Hacking on an lambda endpoint..
Exposes the ETag for cors
Fixes a bug if the bucket is put in the path when using the s3 client
Can POST form upload files

Supported methods

Buckets

Create bucket
Delete bucket
List buckets
List content of buckets (prefix, delimiter, marker and max keys, common prefixes)

Objects

Put object (support for metadata, including ContentEncoding (gzipped files)
Delete object(s)
Get object (including using the HEAD method)
Get dummy ACLs for an object
Copy object (including updating of metadata)
Create Multipart upload, Complete multipart upload.

Quick Start

Install s3rver:

npm install s3rver -g

You will now have a command on your path called s3rver

Executing this command for the various options:

s3rver --help

Supported clients

Please see Fake S3s wiki page for a list of supported clients. When listening on HTTPS with a self-signed certificate, the AWS SDK in a Node.js environment will need httpOptions: { agent: new https.Agent({ rejectUnauthorized: false }) } in order to allow interaction.

Please test, if you encounter any problems please do not hesitate to open an issue :)

Static Website Hosting

If you specify an indexDocument then get requests will serve the indexDocument if it is found, simulating the static website mode of AWS S3. An errorDocument can also be set, to serve a custom 404 page.

Hostname Resolution

By default a bucket name needs to be given. So for a bucket called mysite.local, with an indexDocument of index.html. Visiting http://localhost:4568/mysite.local/ in your browser will display the index.html file uploaded to the bucket.

However you can also setup a local hostname in your /etc/hosts file pointing at 127.0.0.1

localhost 127.0.0.1
mysite.local 127.0.0.1

Now you can access the served content at http://mysite.local:4568/

Tests

When running the tests with node v0.10.0 the following error is encountered. This is resolved by running the tests with v0.11.*. I recommend using NVM to manage your node versions.

To run the test suite, first install the dependencies, then run npm test:

$ npm install
$ npm test

Programmatically running s3rver

You can also run s3rver programmatically.

This is particularly useful if you want to integrate s3rver into another projects tests that depends on access to an s3 environment

Example in mocha:

var S3rver = require('s3rver');
var client;

before(function (done) {
    client = new S3rver({
        port: 4569,
        hostname: 'localhost',
        silent: false,
        directory: '/tmp/s3rver_test_directory'
    }).run(function (err, host, port) {
        if(err) {
         return done(err);
        }
        done();
    });
});

after(function (done) {
    client.close(done);
});

fromkeith/s3rver