# S3 buckets containing periods not allowed

**URL:** <https://meta.discourse.org/t/s3-buckets-containing-periods-not-allowed/35645>\
**Category:** Feature\
**Created:** [November 16, 2015, 1:23pm UTC](https://meta.discourse.org/t/s3-buckets-containing-periods-not-allowed/35645 "2015-11-16T13:23:32Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![uppfinnarn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/uppfinnarn/32/121981_2.png) [@uppfinnarn](https://meta.discourse.org/u/uppfinnarn)\
**Post date:** [November 16, 2015, 1:23pm UTC](https://meta.discourse.org/t/s3-buckets-containing-periods-not-allowed/35645/1 "2015-11-16T13:23:32Z")

</div>

So, with the introduction of the `s3_cdn_url` setting, you can set a custom URL to be used instead of the long S3 URL.

Unfortunately, `s3_upload_bucket` doesn’t allow periods in the name… which means that if I, as per Amazon’s documentation, create a bucket called [static.example.com](http://static.example.com) and point a CNAME to it, I can set Discourse to print out URLs to [static.example.com](http://static.example.com), but I can’t set it to actually upload to that bucket.

(I want to put Cloudflare in front of a CNAME, making for a low-cost but effective CDN. It’s not just for looks.)

---

_[View the full topic](https://meta.discourse.org/t/s3-buckets-containing-periods-not-allowed/35645)._