# Backup to S3 configuration problem

**URL:** https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571
**Category:** Support
**Created:** [January 9, 2018, 10:54am UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571 "2018-01-09T10:54:51Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![supervazi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supervazi/32/86890_2.png) [@supervazi](https://meta.discourse.org/u/supervazi)
#### Post date: [January 9, 2018, 10:54am UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/1 "2018-01-09T10:54:51Z")

</div>

Configuring automatic backups conform this topic:

> [@Configure automatic backups for Discourse](https://meta.discourse.org/t/configure-automatic-backups-for-discourse/14855):
>
> bookmark This guide explains how to configure automatic backups for Discourse, including storage options on local servers and S3-compatible storage. Learn how to set up automatic backups for your Discourse platform. This guide covers configuring automatic backups, storing them on local servers or S3-compatible storage, and managing storage retention options like Amazon Glacier. Configuring automatic backups Navigate to /admin settings. Select the Backup section. Set backup\_frequency to …

When I want to enter my s3 bucket name I get the following error:

s3\_backup\_bucket: Value doesn’t match the required format.

The bucket I use exists, it is accessible with the credentials entered in “Files” section, as mentioned in the topic. We have a bucket naming standard and conform that I need to name my bucket in the following format:

[bucket-purpose].[domainname]

So, this backup is named: [community-backup.mydomain.com](http://community-backup.mydomain.com)  
I think the problem is with dots in the bucket name.  
Is there any possibility to use my bucket?

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [January 9, 2018, 12:00pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/2 "2018-01-09T12:00:06Z")

</div>

Use hyphens instead of dots?

---

<div class="post-metadata">

### Author: ![supervazi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supervazi/32/86890_2.png) [@supervazi](https://meta.discourse.org/u/supervazi)
#### Post date: [January 9, 2018, 12:47pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/3 "2018-01-09T12:47:02Z")

</div>

A cannot change our internal standard. It is with dots. If it will not work with discourse, than I will need to find other solution to copy backups to S3 (own script).

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [January 9, 2018, 12:50pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/4 "2018-01-09T12:50:03Z")

</div>

> [@supervazi](#):
>
> A cannot change our internal standard.

That’s upto Your own Preferences but the easiest way for You to make it work is to use a relatively standard naming scheme.

> [@supervazi](#):
>
> I will need to find other solution to copy backups to S3.

Sure You Can do that! .

> [@supervazi](#):
>
> (own script).

All the Best!

---

<div class="post-metadata">

### Author: ![supervazi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supervazi/32/86890_2.png) [@supervazi](https://meta.discourse.org/u/supervazi)
#### Post date: [January 9, 2018, 1:24pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/5 "2018-01-09T13:24:49Z")

</div>

Our naming scheme is 100% compliant with Amazon S3 Bucket Naming Requirements, so it is “relatively standard” 😉

> **[General purpose bucket quotas, limitations, and restrictions - Amazon Simple...](https://docs.aws.amazon.com/AmazonS3/latest/userguide/BucketRestrictions.html)**
>
> Restrictions for using general purpose buckets in Amazon S3, including the number of buckets per account and bucket naming guidelines.

If discourse do not allow dots in bucket names, then I cant use its internal copy-to-s3 feature.  
My question was more like: Why this restriction of using dots?

Anyway, thank you for your quick answer. 🙂

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [January 9, 2018, 2:38pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/6 "2018-01-09T14:38:49Z")

</div>

> [@supervazi](#):
>
> Why this restriction of using dots?

If you search ‘s3 bucket dots’ on this forum there are a few topics about it. It looks like it comes down to the lack of HTTPS support on buckets with dots in the name:

> [@Discourse does not allow dot «.» symbol in bucket name while Amazon S3 allows it](https://meta.discourse.org/t/discourse-does-not-allow-dot-symbol-in-bucket-name-while-amazon-s3-allows-it/29251/8):
>
> Yes I agree, we should just disallow this, its adding complexity where complexity is not needed. If people want vanity “sexy” names then can use s3\_cdn. A solution that only works with HTTP is not really acceptable.

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [January 9, 2018, 2:39pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/7 "2018-01-09T14:39:27Z")

</div>

Also, this is From the same AWS Documentation page that You linked above:

- When using virtual hosted–style buckets with SSL, the SSL wildcard certificate only matches buckets that do not contain periods. To work around this, use HTTP or write your own certificate verification logic. We recommend that you do not use periods (“.”) in bucket names.

The following examples are invalid bucket names:

| Invalid Bucket Name | Comment |
| --- | --- |
| `.myawsbucket` | Bucket name cannot start with a period (.). |
| `myawsbucket.` | Bucket name cannot end with a period (.). |
| `my..examplebucket` | There can be only one period between labels. |

---

<div class="post-metadata">

### Author: ![supervazi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supervazi/32/86890_2.png) [@supervazi](https://meta.discourse.org/u/supervazi)
#### Post date: [January 9, 2018, 3:01pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/8 "2018-01-09T15:01:06Z")

</div>

So, our bucket names are valid, but will not work with amazon wildcard cert. And this is why discourse do not accept bucket names with dots.  
Tank you for your help.

---

<div class="post-metadata">

### Author: ![regnatarajan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/regnatarajan/32/67916_2.png) [@regnatarajan](https://meta.discourse.org/u/regnatarajan)
#### Post date: [June 1, 2018, 5:26pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/9 "2018-06-01T17:26:02Z")

</div>

Is there a way to access the backups from bash so we can script our own backups?

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [December 2, 2020, 4:35pm UTC](https://meta.discourse.org/t/backup-to-s3-configuration-problem/77571/10 "2020-12-02T16:35:16Z")

</div>


