I've troubles about using amazon S3 destination option: I receive a mail with Could not run backup because the file could not be saved to the destination message.

On the destination panel the path is: https://XXXXXXXKEYXXXXXXXX@s3.amazonaws.com/mybackups.

It's a module issue or I've to better configure my Amazon S3 ACL?

Thank you.

Comments

ronan’s picture

I have no idea. I haven't used this feature much beyond testing that it works. I can't help you with configuring your ACL but maybe somebody else will have an idea.

R

Funkwarrior’s picture

Thank you ronan, any help, especcially on the ACL, would be really appreciated.

Funkwarrior’s picture

Status: Active » Closed (fixed)

The S3 destination works fine after update my application that manage my account and setting better the ACL.
Thank you ronan.

rowanprice’s picture

I received the same message ("user warning: S3::putObject(): [NoSuchBucket] The specified bucket does not exist in * sites/all/modules/backup_migrate/includes/S3.php on line 357."), and it turns out it was because my bucket didn't follow the rather stringent naming requirements, one of which is that bucket names be *lowercase*. Hope that helps someone.

egifford’s picture

Rowan,

Thanks for the tip! You saved me a few hours of head banging.

--Ed

steveoliver’s picture

Title: Amazon s3 configuration » Amazon S3 Bucket Configuration

That's the ticket (lowercase buckets)! Thanks, Rowan.

beatnikdude’s picture

#4 is it, lowercase bucket names are required.
fixed:
• error trying to backup the database to amazon S3 : "Could not run backup because the file could not be saved to the destination."
• and in the logs: "user warning: S3::putObject(): [NoSuchBucket] The specified bucket does not exist in * sites/all/modules/backup_migrate/includes/S3.php on line 357."

dc_marc’s picture

Lowercase it is! That helped me, too. Thanks!

jienckebd’s picture

#4 worked thanks!