# Digital Ocean Spaces don’t implement the AWS S3 API for the CORS rule

**URL:** <https://meta.discourse.org/t/digital-ocean-spaces-don-t-implement-the-aws-s3-api-for-the-cors-rule/111736>\
**Category:** Self-hosting\
**Tags:** cdn, s3\
**Created:** [15 maart 2019 om 19:37 UTC](https://meta.discourse.org/t/digital-ocean-spaces-don-t-implement-the-aws-s3-api-for-the-cors-rule/111736 "2019-03-15T19:37:13Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [8 maart 2020 om 03:51 UTC](https://meta.discourse.org/t/digital-ocean-spaces-don-t-implement-the-aws-s3-api-for-the-cors-rule/111736/13 "2020-03-08T03:51:18Z")

</div>

I’m writing up on a big experiment using DO services with Discourse (like Redis Service, PostgreSQL service, Object Store service, CDN service), so we can forward this in a concise document. I found a far worse problem already. Their S3-Clone CDN removes the `Content-Encoding` header of files, so you can’t serve our GZip and Brotli Javascript, and it just breaks _everything_.

---

_[View the full topic](https://meta.discourse.org/t/digital-ocean-spaces-don-t-implement-the-aws-s3-api-for-the-cors-rule/111736)._
