S3 restoration instructions are misleading - S3 URI Structure causes errors

Raised as an issue on github (issue 2391), to try to get the documentation updated. Including here so that someone searching for the errors listed below when doing a restore / restore test finds the solution ASAP until the docs are able to be updated.

Docs covering restoration from s3 mailinabox.email/maintenance.html have code snippets for the duplicity command for restoring a MIAB install from an S3 bucket:

Amazon S3 backups
If your backups are stored in Amazon S3, get your account credentials handy and then run a duplicity restore:

export AWS_SECRET_ACCESS_KEY=paste your AWS secret access key here
export PASSPHRASE=$(cat your_backup_secret_key_file.txt)
sudo -E duplicity restore --force s3://s3.amazonaws.com/your-bucket-name/your-backup-path/ ```

The s3:// URI example is misleading, as the S3 URI does not need a FQDN. If you construct a URI in the pattern of the example, it will return errors such as:

Attempt of list Nr. 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden
Attempt of list Nr. 2 failed. AttributeError: ‘NoneType’ object has no attribute ‘objects’

More details of the error can be seen in other posts showing that people hit these errors all the time, following the provided documentation. (unable to post links, so a screenshot will have to do)

The documentation could be updated to reflect the real nature of the s3:// URIs.

Amazon S3 backups
If your backups are stored in Amazon S3, get your account credentials handy and then run a duplicity restore:

export AWS_SECRET_ACCESS_KEY=paste your AWS secret access key here
export PASSPHRASE=$(cat your_backup_secret_key_file.txt)
sudo -E duplicity restore --force s3://your-bucket-name/your-backup-path/ ```

Additionally, the docs could reference the S3 tools (console dot aws dot com) available to copy the needed URIs from the S3 web administration interface:

This topic was automatically closed 40 days after the last reply. New replies are no longer allowed.