# Full Site CDN Using AWS CloudFront

**URL:** https://meta.discourse.org/t/full-site-cdn-using-aws-cloudfront/208161
**Category:** Self-hosting
**Created:** [November 3, 2021, 8:32pm UTC](https://meta.discourse.org/t/full-site-cdn-using-aws-cloudfront/208161 "2021-11-03T20:32:16Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Hyan](https://avatars.discourse-cdn.com/v4/letter/h/5fc32e/32.png) [@Hyan](https://meta.discourse.org/u/Hyan)
#### Post date: [August 30, 2023, 8:06am UTC](https://meta.discourse.org/t/full-site-cdn-using-aws-cloudfront/208161/2 "2023-08-30T08:06:26Z")

</div>

Hi @jaffadog

> [@jaffadog](#):
>
> Do not configure “DISCOURSE\_CDN\_URL”

I’m in the similar scenario but in full site with a different CDN. In your experiment, did you ever test config DISCOURSE\_CDN\_URL with the website domain URL. For example, in full CDN mode, if your website URL is [https://foo.bar.com](https://foo.bar.com); then the CDN URL should be [https://foo.bar.com](https://foo.bar.com) as well. If we leave DISCOURSE\_CDN\_URL empty then website assets url will start with relative path. For example as below snippet,

```plaintext
      <link rel="preload" href="/extra-locales/admin?v=8f522e122c802d1ed66dfa7fecafbb35" as="script">
<script defer src="/extra-locales/admin?v=8f522e122c802d1ed66dfa7fecafbb35"></script>

```

This just looks not elegant in a production website, though both URL make request to [https://foo.bar.com](https://foo.bar.com).

---

_[View the full topic](https://meta.discourse.org/t/full-site-cdn-using-aws-cloudfront/208161)._