|
@@ -145,6 +145,7 @@ $ xxd -g 2 -l 64 -p /dev/random | tr -d '\n'
|
|
|
* `IMGPROXY_MAX_CLIENTS` — the maximum number of simultaneous active connections. Default: `IMGPROXY_CONCURRENCY * 10`;
|
|
|
* `IMGPROXY_TTL` — duration in seconds sent in `Expires` and `Cache-Control: max-age` headers. Default: `3600` (1 hour);
|
|
|
* `IMGPROXY_USE_ETAG` — when true, enables using [ETag](https://en.wikipedia.org/wiki/HTTP_ETag) header for the cache control. Default: false;
|
|
|
+* `IMGPROXY_USE_S3` — when true, enables fetching the images from an `s3` source. See [Serving files from S3](#serving-files-from-s3). Default: false.
|
|
|
* `IMGPROXY_LOCAL_FILESYSTEM_ROOT` — root of the local filesystem. See [Serving local files](#serving-local-files). Keep empty to disable serving of local files.
|
|
|
|
|
|
#### Security
|
|
@@ -229,6 +230,14 @@ imgproxy can process files from your local filesystem. To use this feature do th
|
|
|
1. Set `IMGPROXY_LOCAL_FILESYSTEM_ROOT` to your images directory path.
|
|
|
2. Use `local:///path/to/image.jpg` as the source image url.
|
|
|
|
|
|
+## Serving files from S3
|
|
|
+
|
|
|
+imgproxy can process files from S3 buckets. To use this feature do the following:
|
|
|
+
|
|
|
+1. Set `IMGPROXY_USE_S3` to `true`.
|
|
|
+2. Ensure you pass `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` as environment variables. Other authentication mechanisms supported by the AWS sdk (environment, session, or instance role credentials) are also supported. The credentials need to be able to read from any of the `bucket_name` variables given in the source URLs (see below).
|
|
|
+3. Use `s3://%bucket_name/%object_key` as the source image url
|
|
|
+
|
|
|
## Source image formats support
|
|
|
|
|
|
imgproxy supports only the most popular image formats of the moment: PNG, JPEG, GIF and WebP.
|