Backup to S3 configuration problem

[supervazi (Varadi Zoltan)]

Configuring automatic backups conform this topic:

Configure automatic backups for Discourse

So you’d like to automatically back up all your Discourse data every day? Go to the /admin settings, backup, and set backup_frequency to 1. [image] Now backup will be taken every day. Store backups on local server or Amazon S3 WARNING Storing backups and regular uploads in the same bucket and folder is no longer supported and will not work. By default backups are stored on the local server disk. In order to store backups on Amazon S3, you’ll need to create a unique, private …

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
I think the problem is with dots in the bucket name.
Is there any possibility to use my bucket?

[itsbhanusharma (Bhanu Sharma)]

Use hyphens instead of dots?

[supervazi (Varadi Zoltan)]

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).

[itsbhanusharma (Bhanu Sharma)]

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.

I will need to find other solution to copy backups to S3.

Sure You Can do that! .

(own script).

All the Best!

[supervazi (Varadi Zoltan)]

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

https://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html

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.

[david (David Taylor)]

@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

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.

[itsbhanusharma (Bhanu Sharma)]

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.

[supervazi (Varadi Zoltan)]

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.

[regnatarajan]

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