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

<div class="post-metadata">

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

</div>

As I understood it, periods in the bucket name cause havoc with https and certificates so it is **strongly discouraged** that you do this. Unless you never plan to use https.

> **[Amazon S3 Gotcha: Using Virtual Host URLs with HTTPS](https://shlomoswidler.com/2009/08/amazon-s3-gotcha-using-virtual-host)**
>
> Amazon S3 is a great place to store static content for your web site. If the content is sensitive you’ll want to prevent the content from being visible while in transit from the S3 servers to the client. The standard way to secure the content during...

We ran into many problems with this, which is why it is disallowed. It is not random. It’s a resolution to a problem many Discourse instances faced.

---

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