# S3 buckets containing periods not allowed **URL:** \ **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:** 25
**Author:** ![winterdj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/winterdj/32/248980_2.png) [@winterdj](https://meta.discourse.org/u/winterdj)\ **Post date:** [February 7, 2022, 8:26am UTC](https://meta.discourse.org/t/s3-buckets-containing-periods-not-allowed/35645/25 "2022-02-07T08:26:56Z")
After lots of frustration and Googling, I’ve found this topic, and am surprised to see that it was created back in 2015, and that this is still an issue? It’s a valid use-case to want to use an S3 bucket with periods, and to use the static hosting feature of S3, and then to have CloudFlare in front of this with SSL. There is nothing wrong with this setup, except that Discourse currently prevents us from doing so. If Discourse really wants to nanny all of the other users into protecting themselves against SSL issues with periods in S3 bucket names, then can it at least just display a link to some documentation for them to educate themselves, while also allowing people who know how to configure this correctly to do so? --- _[View the full topic](https://meta.discourse.org/t/s3-buckets-containing-periods-not-allowed/35645)._