s3-nginx-proxy

A feature-rich Amazon S3 NGINX-based proxy, running in Docker and Kubernetes.

Features

• Authentication to private buckets
• Multiple buckets
• Multiple domains per bucket (with shared cache)
• Multiple regions
• Cache duration based on HTTP status
• Auto-reload after every configuration update (in production too)
• Single-key cache purge support (using HTTP DELETE)
• Cloudflare cache purging support
• Third-party S3 providers support
• Observability (Prometheus-compatible)

Usage

Recommended setup is to create an AWS IAM user for each s3-nginx-proxy deployment. You should then attach a policy to exclusively grant it the GetObject permission on the required buckets, such as:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "VisualEditor0",
      "Effect": "Allow",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::thepoon.ppy.sh/*"
    }
  ]
}

Granting too much permissions may lead to security risks (such as listing the entire bucket content). Be careful!

Docker

Edit ./data/etc/proxy-config/virtualhosts.json and ./data/etc/proxy-config/cache.json to match your desired settings. Put your AWS credentials in ./data/etc/proxy-config/secrets.json (see template in ./data/etc/proxy-config/secrets.json.example). Start the NGINX and config generator containers with docker-compose up -d.

Kubernetes (Helm)

Helm chart is available at https://github.com/ppy/helm-charts/tree/master/osu/s3-nginx-proxy

Purge configuration

Single files can be purged from cache using the HTTP DELETE method.

By default, this is enabled to everyone with no authentication.
Authentication can be enabled by setting purgeAuthorizationKey in the cache config and using the HTTP Authorization header.

Cloudflare purging

If Cloudflare is placed in front of s3-nginx-proxy, files can also be purged on Cloudflare's CDN using their API.

It can be enabled by setting the following variables in the cache config:

• purgeCloudflareApiToken must be a purging-enabled token.
  Head to your account's API Keys and create a custom token with the Zone > Cache Purge > Purge permission enabled on the desired zone.
• purgeCloudflareZoneId is found on your domain's home page on your Cloudflare dashboard.

Third-Party S3 Providers

S3 endpoint is computed from the region property if you're using Amazon S3. For other providers, upstream can be used instead.

For example, endpoint for DigitalOcean Spaces in region NYC3 is nyc3.digitaloceanspaces.com.

Be aware however that you will not be benifitting of the added security of the Amazon S3 very granular permissions (may make your bucket listing public!).

Observability

A Prometheus-compatible metrics endpoint can be enabled in metrics.json.
The following metrics are exposed:

• nginx_http_requests_total: Number of HTTP requests (counter)
• nginx_http_request_duration_seconds: HTTP request latency (histogram)
• nginx_http_connections: Number of HTTP connections (gauge)
• nginx_upstream_cache_status: Number of HTTP requests per upstream cache status (counter)

Breaking Changes

2022.705.0

Secrets have been moved to ./data/etc/proxy-config/secrets.json, and key for each secret set need to be added to the virtual hosts config (see default ./data/etc/proxy-config/virtualhosts.json).

Contributing

This project is very bare-bones for now; a sort of Minimum Viable Product.
Planned features are the ability to purge cache (both full and specific key), and more configuration options.

Contributions can be made via pull requests to this repository. We hope to credit and reward larger contributions via a bounty system. If you're unsure of what you can help with, check out the list of open issues.

Note that while we already have certain standards in place, nothing is set in stone. If you have an issue with the way code is structured; with any libraries we are using; with any processes involved with contributing, please bring it up. I welcome all feedback so we can make contributing to this project as pain-free as possible.

Licence

The osu! client code, framework, and server-side components are licensed under the MIT licence. Please see the licence file for more information. tl;dr you can do whatever you want as long as you include the original copyright and license notice in any copy of the software/source.

Please note that this does not cover the usage of the "osu!" or "ppy" branding in any software, resources, advertising or promotion, as this is protected by trademark law.