# 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:** 11

<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:** [6 maart 2020 om 21:08 UTC](https://meta.discourse.org/t/digital-ocean-spaces-don-t-implement-the-aws-s3-api-for-the-cors-rule/111736/11 "2020-03-06T21:08:19Z")

</div>

So the whole topic conclusion was a misunderstanding.

I spent a full day testing Discourse compatibility with DO offerings, and the CORS thing here was a red herring.

The problem is that DO Spaces don’t implement the `tagging` header in their S3 Clone.

Fix for the `upload_assets` task is pretty simple and is in a branch.

[https://github.com/discourse/discourse/commit/5c8e4588000c1fa78af9100004d5f8063722e088](https://github.com/discourse/discourse/commit/5c8e4588000c1fa78af9100004d5f8063722e088)

Problem is that we actually use `tagging` for real in another rake task, so if using DO Spaces you can’t really ever use the `s3:expire_missing_assets` task. Which can be an “okay” trade-off for some.

I plan on updating and creating some new guides on this next week.

---

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