In this article:
Keeping your WordPress backups in a secure, remote location is an important part of keeping your Website safe from harm. With the Total Upkeep plugin’s Premium Extension, you can use Amazon’s Simple Storage Service (S3) to safely store your WordPress backups in case anything happens to your web server.
Why Amazon S3?
Amazon S3 is designed to have 99.999999999% durability and is extremely affordable. With S3, you pay for what you use in a scaling fashion, which makes it a perfect solution for websites of all sizes to keep secure offsite backups.
How to Configure Amazon S3 Storage
- You must already have an AWS account set up in order to follow these instructions.
- Sign into your AWS Management Console, and navigate to Security, Identity, and Compliance ➡ IAM.
- Click on Users in the left-hand menu, then click Add User.
- Name your new user and click Programmatic Access, then click Next: Permissions.
- Choose Attach existing policies directly.
- Type AmazonS3FullAccess into the filter and select the matching policy, then click Next: Tags.
- Click Next: Review, then Create User.
- Copy the Access Key ID and Secret Access Key to a safe location. This is the only time you will have access to them without creating new credentials.
- Log into your WordPress Dashboard and navigate to Total Upkeep ➡ Settings ➡ Backup Storage.
- Next to Amazon S3, click Configure.
- Paste your Access Key ID and Secret Access Key into the corresponding fields, and click Save Settings.
- Exit the pop-up settings menu, check the box next to Amazon S3, and click Save Settings.
Using an s3-compatible Storage Service
You can also use Total Upkeep Premium for any S3-Compatible storage service, but the interface is a little confusing because it was originally designed for DreamHost’s DreamObjects service, which is an S3-Compatible object storage service.
You can set up your S3-Compatible storage service by navigating to Total Upkeep > Settings > Backup Storage and selecting the option to Configure DreamObjects. From there, you’ll just need your Access Key and Secret, as well as the hostname of your storage, and you’ll be able to store your backups there.
Congratulations! Your WordPress Backups will now be securely saved on Amazon S3 so you can rest easy knowing your website is safe.
Total Upkeep Premium
3 Remote Storage Options
Additional Tools + Single File Restorations
BUY NOW FOR $2.50/MO
View Premium Features >>
These instructions require the Premium Upgrade.
11 thoughts on “How do I upload my WordPress backup to Amazon S3?”
Will the changes announced by Amazon regarding S3 bucket security have any affect on Total Upkeep?
I’m not completely sure how or if the changes to Amazon S3 will effect Total Upkeep but if you can link us to the source of where you found this information I can get it over to our developers and have them review it and give us a sure answer.
Thanks a lot!
Thanks for this; both are awesome options, and I think we will start with Google Drive due to the size of our backups and nature of business, and then look into AWS if/when we grow to need more storage, so appreciate you providing both options 🙂
Thanks for the steps, look easy enough to follow 🙂
I’ve got Total Upkeep Premium and want to do remote storage to Amazon S3, but completely lost on the AWS site with all it’s plan/tiers/options!
We don’t have a very large website, and really just want remote backups in case anything goes wrong. Do you have any advice about which plan to use please? Or what we should be looking for in terms of performance etc?
This one seems to be ok, but that would just be a wild guess!
ALWAYS FREE – Amazon DynamoDB – 25 GB of storage
Fast and flexible NoSQL database with seamless scalability.
The DynamoDB NoSQL won’t work for object storage, you’ll need to select S3 (Simple Storage Service) to store your backups. Depending on how often you make new backups and download your stored ones, S3 can be extremely affordable. However, if you’re looking for a completely free option, I’d recommend checking out Google Drive, which is free up to 15GB of storage.
Could you list exact permissions for IAM role?
AmazonS3FullAccess is not good in terms of security.
You can build a custom role with these permissions:
You can omit the DeleteObject and DeleteObjectVersion if you want to manage your backup retention yourself, rather than letting the plugin delete old backups for you. You can also strengthen this permission set by creating the bucket yourself, and specifying the bucket name in your Total Upkeep settings, then only allowing the permissions to that specific bucket (replace */* with mybucket/*). Then you can also omit the CreateBucket permission.
why ListAllMyBuckets is still necessary if I provide pre-existing bucket?
same for CreateBucket I guess
I haven’t tested the permissions without ListAllMyBuckets, it’s possible that might have an error or at least a warning when it searches your account for the right bucket. You don’t need CreateBucket as long as you’ve specified the bucket name for a bucket you’ve already created. Let us know if you try it without ListAllMyBuckets and it works for you or if you have any issues.
These instructions do not seem to work with AWS S3 Glacier. Am I correct? Do you plan to add that capability?
At this time, Total Upkeep can’t automatically save to a Glacier “Vault” the same way that it saves to an S3 “Bucket,” but if you would like to utilize this lower-cost storage option, you can use Amazon’s Lifecycle Management features to automatically transition your backup storage from your buckets to your vaults.