I have been reading about several issues regarding this and I have already:

1. Downloaded the 0.4 version and installed them into backup_migrate/includes
2. Made sure the bucket is all lower case
3. Checked my ACL on S3 - I have even put as test Everyone can upload/delete

On my log, the only thing that gives me is (and also if I try to perform a one off quick backup)

Could not run backup because the file could not be saved to the destination. (Error)

Can someone help me out here please?
Thank you

Comments

kappaluppa’s picture

Same exact problem. Any solution on this?
Thanks,
K

jking1224’s picture

I had this problem initially. I then tested adding an "Everyone" permission to the bucket. and that worked. But I don't want to run that way. So, I added "Authenticated Users" can upload/delete to the bucket and removed the "Everyone" permission from the bucket. That worked.

I also have IAM permission set into a group and that group has full s3 action permission on the bucket.

I can also confirm the the S3.php version 0.4 worked as well as the 0.5.1-dev version.

ronan’s picture

Status: Active » Postponed (maintainer needs more info)

I have not had this issue in my testing. Can you think of any other info that might be relevent?

mermentau’s picture

I was fighting this problem and adding an Amazon "Secret Access Key" did the trick with version 7.x-2.8. I have a very similar drupal 7 site set up on the same VPS that's been working fine with B&M and Amazon S3. I thought it would be quick and easy to copy all the same settings in Drupal. The original site that's working fine does not use the "Secret Access Key". The second site wouldn't work without it.

I'll be looking at using the IAM access setup as #2 did as it appears that's favored by AWS now.

dman’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (works as designed)

(Old, but)
@mermentau - the working site certainly would have required and used a secret access key. It's jut that when you revisit the settings screen, that 'secret' is not shown to you and the field appears blank. The UI could probably be more helpful about that, as it confused me also, and I was nervous about re-saving a blank value there.

In related news, I have posted a walkthrough for setting up Backup and Migrate - with AWS S3 with some troubleshooting notes for the access control lists. I found a gotcha there also.

mistermastermatt’s picture

Is it just me, or has this suddenly become a problem again? I have several sites backing up to S3 and they have all suddenly decided to stop working with the error mentioned by the OP. I made no changes to the sites at all and no changes to S3 or IAM within AWS.
Anybody else having this problem?

mistermastermatt’s picture

Status: Closed (works as designed) » Active
mistermastermatt’s picture

Category: Bug report » Support request
Priority: Critical » Normal
mermentau’s picture

My S3 backups are working fine today.

Anonymous’s picture

Ideally you should only permit authorized users to create or list backups to S3 buckets, unless you really want Joe Public to be able to get all your user details.

Rather than allow users access from the (very limited) user permissions properties in S3 try creating a bucket policy at http://awspolicygen.s3.amazonaws.com/policygen.html

couturier’s picture

Status: Active » Postponed (maintainer needs more info)

Can anyone report if this is still a problem with newest upgrades?

couturier’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)

Closing after more than two weeks with no activity.

dhruveshdtripathi’s picture

I'm facing the same issue in the latest 7.x-3.5 version.

Getting following error:

User warning: S3::putObject(): [InvalidRequest] The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. in S3::__triggerError()

Our s3 cloud is hosted on india region. Is this error related to that? If yes, please let me know how to fix this.

I've been searching the solution since last few days but couldn't find proper solution for this.

Also please let me know which versions of s3-php library and awssdk needed with 7.x-3.5 versions.

Looking forward for solution ASAP.

Thanks in advance.

DamienMcKenna’s picture

@dhruveshdtripathi: Please open a new issue for this instead of continuing a closed issue. Thank you.

rfay’s picture

FYI I had this problem because my backup size exceeded the S3 object max size of 5GB, see https://stackoverflow.com/questions/26319815/entitytoolarge-error-when-u...

This only happened on production, where I have limited access, so I worked on it by adding code to the module.

I added

      watchdog("backup_migrate", "About to push s3 file %filepath size %size", array("%filepath" => $file->filepath(), "%size" => filesize(($file->filepath()))), WATCHDOG_INFO);

into _save_file() in destinations.s3.inc (right before line 25, where the s3->putObject() is done) and that explained the situation.

I was able to discover basic problem only by running `drush cron -v` to get a reasonable message about the problem.

In the end, it was that at some point backup_migrate backups were including previous backup_migrate backups, which doubled the size and it grew exponentially.