# Incorrect S3 warning in admin menu

**URL:** https://meta.discourse.org/t/incorrect-s3-warning-in-admin-menu/174496
**Category:** Bug
**Created:** [December 29, 2020, 2:02pm UTC](https://meta.discourse.org/t/incorrect-s3-warning-in-admin-menu/174496 "2020-12-29T14:02:23Z")
**Posts on this page:** 1
**Showing post:** 5

<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: [December 29, 2020, 5:37pm UTC](https://meta.discourse.org/t/incorrect-s3-warning-in-admin-menu/174496/5 "2020-12-29T17:37:26Z")

</div>

Yes, the idea is that using S3 without a CDN is a obvious mistake and everyone that is paying for S3 in a production instance can afford to pay for S3 **and** a CDN for less money.

One possible workaround if you are somehow stuck in S3 without a CDN is setting `s3 cdn url` to the bucket URL, so it becomes a noop.

---

_[View the full topic](https://meta.discourse.org/t/incorrect-s3-warning-in-admin-menu/174496)._