Support

WeTransfer is neither a practical nor secure way for storing backup archives. In fact it's far from being practical or secure!

A backup archive can consist of multiple files (parts). Each file would need to be transferred separately. This creates a few problems when considering WeTransfer or any other file transfer (not storage!) service.

The most important problem is that a backup archive may consist of several files (parts), each one of which needs to be uploaded separately. Moreover, each file needs to be deleted as soon as it's uploaded for your use case to make any sense. In fact, the only way your use case would make sense is if using WeTransfer forced "Upload each part immediately" to be always enabled.

This means that as the backup progresses we create an archive part, we upload it to WeTransfer, we get a URL and we store it temporarily. If uploading to WeTransfer fails midway through the backup – for several reasons we've seen that I could fill a sizable book with – these files are lost forever. This violates the Akeeba Backup rule of making it possible for the users to always be able to manually retrieve their backup archive parts, even if these files are in disparate places.

The next problem is that while you propose this as a secure solution, I'm afraid it's not for two reasons.

First, it's just an upload to an Amazon S3 bucket. Worse, it's an upload to someone else's Amazon S3 bucket. It's not under your control.

Second, you are sending a pre-authenticated URL over unencrypted email. Anyone intercepting the email can download this file and you are none the wiser.

If you are really concerned about storage space and security you should be using Upload to Amazon S3. Create a private bucket. Create a new Amazon IAM user with write-only privileges to the bucket. Set up Akeeba Backup's Upload to Amazon S3 with the credentials of this limited user. Set Upload each part immediately to Yes and set a small backup part size (you will need up to 2.5 times that much disk space during backup). Your backups are in a private bucket that only you can access. Your site does not have the ability to download these files so even if it's compromised the files won't be downloaded (they can be erased, though). You can download the files to your local computer using a GUI tool such as CloudBerry Explorer or a CLI tool such as s3cmd. Either way, you can use temporary credentials, generated through Amazon IAM, so if you suspect they're compromised you can kill them immediately. Nothing is sent by email, nothing visible to an attacker can be used to compromise your site. Even if an attacker knows the bucket name and object name (file path) in the bucket they can do nothing since they don't have your keys. This is the most space efficient and secure solution, not WeTransfer or any file transfer service.