# Extend S3 configuration for other S3 API compatible services

**URL:** <https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371>\
**Category:** Feature\
**Created:** [21.Июнь.2018 07:10:42 UTC](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371 "2018-06-21T07:10:42Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [27.Июнь.2018 12:58:06 UTC](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371/9 "2018-06-27T12:58:06Z")

</div>

> [@arrowcircle](#):
>
> There are should be some changes in nginx template. Its better to serve files via nginx, not directly from spaces. Also, its strongly recommended to add nginx caching to make minimum number of read requests to spaces API.

Shouldn’t everyone using S3-like services use a CDN? We even have a separate setting `DISCOURSE_S3_CDN` so people can have a s3-like only CDN.

Maybe after we merge the PR we can work out an optional template with nginx caching and another one using CDNs (Cloudflare should fit here, since it will be caching only statics).

---

_[View the full topic](https://meta.discourse.org/t/extend-s3-configuration-for-other-s3-api-compatible-services/90371)._
