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

<div class="post-metadata">

**Author:** ![delta](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/delta/32/178592_2.png) [@delta](https://meta.discourse.org/u/delta)\
**Post date:** [April 28, 2020, 10:21pm UTC](https://meta.discourse.org/t/s3-buckets-containing-periods-not-allowed/35645/10 "2020-04-28T22:21:16Z")

</div>

I just wanted to add my +1 for allowing periods in S3 bucket names within Discourse. AWS itself allows ([indeed instructs](http://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html#VirtualHostingCustomURLs)) this now for CNAME-based access to S3 content, and provided the `s3_cdn_url` setting in Discourse is utilized so far as I can tell the previous issues encountered around HTTPS are rendered non-problematic, at least when services such as Cloudflare are used (as @uppfinnarn notes SNI-based SSL certs solve this issue).

Might it be possible to revisit this in an upcoming release?

Thank you for a great product!

---

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