Amazon S3 bucket names with dots

Yes, you can create buckets with dots in their name via the AWS Console (web) as well as via AWS cli tools, etc. According to the official AWS documentation (see link below) bucket names must comply with DNS naming conventions, which explicitly allows dots:

[...] Bucket names must be at least 3 and no more than 63 characters long. Bucket names must be a series of one or more labels. Adjacent labels are separated by a single period (.). Bucket names can contain lowercase letters, numbers, and hyphens. Each label must start and end with a lowercase letter or a number [...].

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

I tried using buckets in US as well as eu-central-1 (also see issue 37935). Both are not working, but different error messages.

When you tested with the US bucket - did you install AWS's CLI? https://aws.amazon.com/cli/

Hi Jamie,

Thanks for testing and checking this. It's much appreciated. Please find my tests below.

Bucket name: 1441455056, bucket location: us-east-1

Location checked with:

and:

AWS access credentials for "aws CLI" are configured using "aws configure". Bucket is accessible using:

Nothing is configured under: Virtualmin -> Backup and Restore -> Cloud Storage Providers (output below)

However: Virtualmin -> Backup and Restore -> Amazon S3 Buckets ...shows the list of all buckets available.

A scheduled backup is configured as:

If I trigger a backup via: Virtualmin -> Backup and Restore -> Scheduled Backups -> Action: Backup -> Backup Now, this works perfectly fine.

Then, I created two new buckets:

I changed the configuration: Virtualmin -> Backup and Restore -> Scheduled Backups -> edit the existing one

-> Save Schedule -> Actions: Backup -> Backup Now

No errors, all good. I update the configuration again: Virtualmin -> Backup and Restore -> Scheduled Backups -> edit the existing one

-> Save Schedule -> Actions: Backup -> Backup Now

Error (it looks like virtualmin does not use aws CLI for the backup):

Then, I created a third bucket in eu-central-1:

...and changed the config to use this bucket:

...triggered the backup and this works, too. So my conclusion is that it's the dot in the bucket name (see issue 37935). Do you agree?

The server is still in "testing mode" and not in production. So, feel free to tell me what you want me to do if there is anything I can do to help you.

Today I had the time to investigate this issue further. I removed all previous configuration and started from scratch again. It definitely looks like the dot in the bucket name causes an issue (at least in the European region - I have not tested other regions).

Step 1: everything is clean

Virtualmin -> Backup and Restore -> Amazon S3 Buckets: No scheduled backups to S3 have been created yet, and no default S3 keys have been set.

Virtualmin -> Backup and Restore -> Cloud Storage Providers: "Not yet configured" and "Not used by any backups" (both AWS and Rackspace)

Virtualmin -> Backup and Restore -> Scheduled Backups: No scheduled backups have been created yet.

Step 2: test aws-cli (command line)

Create a new bucket and upload a test file:

Step 3: configure backup in virtualmin

Virtualmin -> Backup and Restore -> Scheduled Backups -> Add a new backup schedule

Destination: Amazon S3 bucket

Access key ID: **********

Secret key ID: **********

Bucket and path: eu.virtualmin.test/backup

-> Create Schedule

Step 4: trigger backup

Virtualmin -> Backup and Restore -> Scheduled Backups

Under Actions -> Backup.. -> Backup Now

Step 5: use bucket name without a dot

Execute exactly the same commands as in step 2, but use euvirtualmintest rather than eu.virtualmin.test.

In Virtualmin -> Backup and Restore -> Scheduled Backups -> ...

Change "Bucket and path" to: euvirtualmintest/backup and save.

Finally, trigger backup as in step 4 again.

Backup runs through without any problems and the following command lists the backup files created:

Awesome!! Many thanks.