s3helper signs S3 object requests using instance credentials. It only accepts connections from 127.0.0.1 and only accepts GET and HEAD methods. It provides no crossdomain.xml (though this can be put in the S3 bucket).
The glide vendoring is used by our build system which relies on https URLs and API keys to access private repos. Sometime after making this public we will drop the use of glide for this, at which point we will also remove the vendoring from this repo.
Clone this repo, then:
$ cd s3-helper
$ go get
$ go build
Create a config in
s3-helper.yml. Start the service with:
$ ./s3-helper -config s3-helper.yml
Run "s3-helper -h" which list possible flags.
s3helper reads its configuration from a file in yml format. The default location is /mob/etc/s3-helper.yml, but this can be changed with the -config option, e.g. "-config=./test.yml"
listen: <endpoint, default is ":8080"> logging: ident: <syslog ident, default is "s3-helper"> level: <syslog level, default is "info"> concurrency: <explicit runtime concurrency, default is 0 which makes it match # of CPUs> statsd_addr: <default is "127.0.0.1:8125"> statsd_env: <default is "dev"> newrelic: name: <newrelic name, default is ""> license: <newrelic license, default is ""> s3_bucket: <name of S3 bucket to forward object requests to> s3_region: <region of S3 bucket> s3_path: <optional prefix to prepend to object requests> s3_retries; <maximum number of S3 retries> s3_timeout: <timeout for S3 requests>
Assume the configuration consists of:
s3_bucket: evs-dev s3_region: us-west-2 s3_path: /chris s3_timeout: 3s s3_retries: 3
s3helper receives an HTTP request from 127.0.0.1, e.g.
It takes this request and maps it to an S3 bucket URL,
This request is signed using the EC2 instance credentials for its first AMI role.
An http GET request for this is made.
The result is forwarded and the following headers retained:
Range requests are fully supported. As a note, Range requests produce 206 responses from S3, and these are faithfully forwarded.
Any amazon specific headers are removed.
Setting s3_timeout causes requests to fail after a specific time. We've found a very small number of S3 requests will take an extraordinary long time for a response and simply retrying them yields a prompt response. s3_retries sets the number of timeout retries (other errors are not currently retried).
This permits e.g. use of nginx in front of s3helper without nginx having to know a single thing about S3, credentials, or magic headers.
s3helper outputs stats for object retrieval times and request counts to the configured statsd/collectd endpoint. If the address and env are set to "" (the default) no stats are emitted.
Basic request metrics are forwarded to New Relic if either the license or name is non-empty. (Default is "", meaning nothing is forwarded.) Requires running the nr-agent on the host and an NR account. It's what we mainly rely on here at Ellation.
Released under the MIT License. See LICENSE.md