Backups & maintenance · Guide
How to Back Up WordPress to Amazon S3

Short answer
To back up WordPress to Amazon S3, create an S3 bucket with public access blocked, then create a dedicated IAM user with a policy that allows access to that bucket only. Install UpdraftPlus, pick Amazon S3 as the remote storage, and enter the access key ID, secret access key and bucket name. Set a schedule for files and the database, run a manual backup once, and check that it appears in S3.
Key takeaways
- An S3 backup needs three things: a bucket, a dedicated IAM user with a narrow policy, and UpdraftPlus connected with access keys.
- Keep Block all public access enabled on the backup bucket so backup files stay private.
- S3 Standard costs $0.023 per GB per month for the first 50 TB in the US East region.
- Back up the database more often than files, and keep 4 file backups and 14 database backups as a starting point.
- New AWS accounts get up to $200 in credits over 6 months, which can cover early backup storage.
What do you need before you back up WordPress to Amazon S3?
You need an AWS account, a WordPress site with admin access, and the free UpdraftPlus plugin installed before you can send backups to Amazon S3.
During AWS registration you provide contact details, payment information and a phone number for account verification, as the TeamUpdraft guide to S3 backups explains. Turn on multi-factor authentication for the AWS account before you go further, since the account holds your backups.
You only need two AWS services for this job: Amazon S3, where the backups live, and Identity and Access Management (IAM), which controls how UpdraftPlus connects to the bucket. UpdraftPlus has over 3 million active installations, according to TeamUpdraft, so its S3 settings are well documented.
A complete backup has two parts, files and database, and WordPress.org stresses that you need both to restore a typical site. Our guide to how to back up WordPress covers the full picture if you want the basics first.
How do you create an S3 bucket for WordPress backups?
Create a bucket in the S3 console, give it a unique name, pick a region near your server, and keep public access blocked.
Open the AWS Management Console, search for S3, and click Create bucket. Bucket names must be unique across all of AWS, so include your domain name in the name. TeamUpdraft advises using only lowercase letters, numbers and hyphens in the name.
Pick the AWS region closest to your website or your main audience. Keep Block all public access enabled so your backup files cannot be reached by anyone on the internet.
How do you set up an IAM user with access to only that bucket?
Create a custom IAM policy that allows access to one bucket only, then attach it to a new IAM user and generate access keys.
Do not connect UpdraftPlus with your main AWS account keys. The UpdraftPlus documentation warns that master keys can do anything to any bucket in the account, so a dedicated user with narrow rights is the safer choice.
Open IAM from the AWS console and select Policies > Create policy. Choose the JSON editor and paste in a policy that names your bucket, with the actions s3:PutObject, s3:GetObject, s3:DeleteObject and s3:ListBucket, as shown in the TeamUpdraft guide to S3 backups. Give the policy a clear name, such as WebsiteBackupPolicy, and save it.
Next, open Users in IAM and click Create user, with a name such as WebsiteBackupUser. Attach the custom policy when asked. Then open the user, go to the Security credentials tab, and create an access key, choosing Application running outside AWS when asked how the key will be used.
AWS will show an access key ID and a secret access key. Save both in a password manager right away, because AWS only displays the secret access key once. If you lose it, you must generate a new key.
How do you connect UpdraftPlus to Amazon S3?
Install UpdraftPlus, open its Settings tab, pick Amazon S3 as the remote storage, and enter the access key, secret key and bucket name.
Log in to WordPress and go to Plugins > Add New Plugin. Search for UpdraftPlus, click Install Now, then Activate. Open Settings > UpdraftPlus Backups and go to the Settings tab.
In the remote storage section, click the Amazon S3 icon. Enter the access key ID, the secret access key and the bucket name in the fields that appear. The UpdraftPlus documentation notes that the S3 location field takes only the bucket name, and that a bucket that does not exist yet will be created for you.
Leave the storage class set to Standard unless you have a specific reason to change it. Then click Test Amazon S3 Settings to check the connection. A success message means UpdraftPlus can reach your bucket, while a failure usually means the bucket name or one of the keys has a typo or an extra space.
How do you schedule automatic backups to S3?
Set separate schedules for files and the database on the UpdraftPlus Settings tab, choose how many copies to keep, and save the changes.
Your database changes more often than your files, since it stores posts, pages, comments, users and settings. TeamUpdraft suggests daily file and database backups for blogs and online stores, weekly files with daily databases for business sites, and monthly files with weekly databases for brochure sites.
For many business sites, keeping 4 file backups and 14 database backups gives a good balance between restore points and storage use, according to TeamUpdraft. As new backups arrive, UpdraftPlus removes older ones based on the retention numbers you set.
WordPress.org recommends backing up small sites once a week and high-activity sites daily, and keeping at least 3 to 5 recent backups in different places. Pick a schedule that fits how often you back up WordPress for your own site, then click Save Changes.
Run one manual backup first to prove the setup works. Open the Backup / Restore tab, click Backup Now, and tick the boxes for database, files and remote storage. The finished backup should appear under Existing Backups with the Amazon S3 icon next to it.
How much does it cost to store WordPress backups in S3?
S3 bills by use, so a small site often costs only a few cents a month, with storage as the main charge.
Amazon lists S3 Standard at $0.023 per GB per month for the first 50 TB in the US East region, on the Amazon S3 pricing page (checked November 2026). A 10 GB backup set in Standard storage therefore costs about $0.23 a month for storage alone, before request charges.
New AWS accounts receive up to $200 in credits over 6 months, with $100 given at once and up to $100 more earned as you use key services, according to the AWS Free Tier page (checked November 2026).
| Storage class | Price per GB per month | Minimum storage | Best for backups |
|---|---|---|---|
| S3 Standard | $0.023 | None | Backups you may restore soon |
| S3 Standard-IA | $0.0125 | 30 days | Backups restored about once a month |
| S3 One Zone-IA | $0.01 | 30 days | Backups you can rebuild if lost |
| S3 Glacier Instant Retrieval | $0.004 | 90 days | Archives read about once a quarter |
| S3 Glacier Flexible Retrieval | $0.0036 | 90 days | Archives read about once a year |
| S3 Glacier Deep Archive | $0.00099 | 180 days | Archives kept for years |
The prices in the table come from the Amazon S3 pricing page (checked November 2026). Cheaper classes add retrieval charges and minimum storage times, so a class that looks cheap can cost more if you restore often.
Two details from the same pricing page matter for small backups. S3 Standard-IA and One Zone-IA charge for a minimum billable object size of 128 KB, and objects deleted before the 30-day minimum still incur a pro-rated charge for the remaining days. Glacier classes carry minimum storage of 90 days, or 180 days for Deep Archive.
Which S3 storage class should you use for backups?
Use S3 Standard for backups you may restore soon, and move older copies to a cheaper archive class with a lifecycle rule.
S3 Standard has no retrieval charge and no minimum storage time, which suits a backup you might need at short notice. It costs $0.023 per GB per month for the first 50 TB, as listed on the Amazon S3 pricing page (checked November 2026).
S3 Standard-IA costs $0.0125 per GB per month, but it adds a retrieval charge and a 30-day minimum, so it fits backups you restore rarely. S3 Glacier Deep Archive costs only $0.00099 per GB per month, yet it carries a 180-day minimum and restores take hours, so it fits copies you keep for the long term and almost never open.
The safest setup, described in the UpdraftPlus S3 documentation, adds three extras. Enable versioning on the bucket so an overwritten backup keeps its earlier version.
Remove the two delete permissions from the IAM policy so the plugin cannot delete old backups. Then use an S3 lifecycle rule to move or delete older backups on a set schedule.
If you are unsure where S3 fits among your options, read where to store WordPress backups before you commit to one place.
How do you restore a WordPress site from an S3 backup?
Open the UpdraftPlus Backup / Restore tab, find the backup set with the S3 icon, and click Restore to download and restore it.
UpdraftPlus downloads the backup files from S3 and restores them to your site. You can restore the whole site or pick single parts, such as the database, plugins, themes or uploads. That choice helps when only one part broke, for example after a bad plugin update.
After the restore finishes, check that the site loads, log in to the admin area, and open a few key pages. Our guide to how to test a WordPress backup lists the checks worth running after any restore.
If you used the strict IAM setup without delete rights, fetch the backup set straight from the S3 console instead, as the UpdraftPlus documentation advises. In that setup the plugin cannot delete old backups, so you manage old copies with lifecycle rules in S3.
What should you do if the S3 backup fails?
Check the keys, bucket name and IAM permissions first, then run the connection test again before you change anything else.
The most common cause is a wrong bucket name or an extra space pasted into a key. The TeamUpdraft guide notes that the test fails when the bucket name does not match exactly, so compare each value character by character.
A second common cause is a policy that misses a needed action. The policy must allow s3:ListBucket on the bucket and s3:PutObject, s3:GetObject and s3:DeleteObject on the objects inside it, as shown in the UpdraftPlus documentation. If any action is missing, uploads or restores will fail.
One odd result is normal in the strict setup. The connection test creates a test file and then tries to delete it, so it reports that it could not delete the file. The UpdraftPlus documentation says this is expected when the IAM user has no delete rights, and you can ignore it.
If the test passes but scheduled backups still fail, look at the UpdraftPlus log for the exact error and the time it stopped. Our guide to fix UpdraftPlus backup failed walks through the common causes one by one.
Frequently asked questions
Is Amazon S3 free for WordPress backups?
Not in the long term. New AWS accounts get up to $200 in credits over 6 months, but after that you pay for the storage, requests and data transfer you use. A small site often costs only a few cents a month, since S3 Standard is $0.023 per GB per month.
Can I use my main AWS account keys with UpdraftPlus?
You can, but you should not. Master keys can reach every bucket in the account, so a stolen key puts all your AWS data at risk. Create a dedicated IAM user with a policy that allows access to the backup bucket only.
Which S3 storage class is best for WordPress backups?
S3 Standard is the best starting point, because it has no retrieval charge and no minimum storage time. Move older copies to Glacier Deep Archive with a lifecycle rule if you want the lowest storage cost and rarely restore them.
How do I know my S3 backup worked?
Run a manual backup from the UpdraftPlus Backup / Restore tab and check that it appears under Existing Backups with the S3 icon. Also open the S3 console and confirm the backup files are in your bucket.
What happens if I delete the IAM user by mistake?
UpdraftPlus loses access to the bucket, so scheduled backups fail until you create a new user and keys and enter them in the plugin settings. Your existing backups stay in S3, since deleting the user does not delete the bucket.
Sources
- Amazon S3 Pricing Amazon Web Services
- AWS Free Tier Amazon Web Services
- How to Backup WordPress to Amazon S3 TeamUpdraft
- Configure Amazon S3 for UpdraftPlus TeamUpdraft Documentation
- Backups WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.


