# Digital Ocean Spaces não implementa a API AWS S3 para a regra CORS

**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:** [Março 15, 2019, 7:37pm 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:** 5

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [Março 15, 2019, 7:53pm UTC](https://meta.discourse.org/t/digital-ocean-spaces-don-t-implement-the-aws-s3-api-for-the-cors-rule/111736/5 "2019-03-15T19:53:22Z")

</div>

No, I really mean assets (uploads seem fine). It seems that when `GlobalSettings.s3_cdn_url` is defined, discourse expects assets (i.e., the javascript stuff) to be in the S3 CDN, so the site is broken because none of the assets are available.

> [@codinghorror](#):
>
> this topic makes very little sense the way it is phrased now.

It makes zero sense to me either. ☹

I just set SiteSettings.s3\_cdn\_url (not in GlobalSettings) and assets seem to still be coming from the server, not the CDN. So maybe it’s a bug with `GlobalSettings.s3_cdn_url`?

Yup. Re-setting the value in `discourse.conf` does this:

 ![image](https://global.discourse-cdn.com/meta/original/3X/e/8/e8cae769228b20f3d52b63e4f9b2ac6e3fa15149.png)

All those red things link to the CDN for the assets.

I turned it back on/off and defining it as a global makes assets link to the `s3_cdn_url`.

So I guess the thing to do is configure those values in a plugin and hide them from the UX that way.

---

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