How to route Pagely site backups to your own S3 bucket

All of your WordPress sites on Pagely are automatically backed up nightly and made available for download via your Atomic dashboard interface. Did you know you can set it up so your backups also automatically accrue under your own Amazon S3 account?

There are a number of reasons why you might want to do this, the primary two being:

1. You want to keep your backups for longer than the 14 days we retain them.
2. Your company requires that you keep all backups on-site behind your company firewall.

In this tutorial I show you the steps necessary to make it so your backups go to your AWS S3 account. In a future post we’ll cover some of the more advanced things you can do such as:

• Creating your own custom retention policies to expire old backups and conserve costs.
• Setting up a rule to push backups over X days old to AWS Glacier for long-term storage saving additional costs on long-term retained backups.
• Creating a process for automatically pulling down nightly backups so a copy resides behind your company firewall.

But first thing is first: If you haven’t already done so, create your AWS account on Amazon. Then follow the steps in this video:

This is the code you will need to paste and edit for your security policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1467134621000",
"Effect": "Allow",
"Action": [
"s3:PutObject"
],
"Resource": [
"arn:aws:s3:::pagely-example-s3-backup-bucket/*"
]
}
]
}


Allow 1-2 days for backups to begin accruing once you’ve filed the support ticket supplying us with your credentials.

Hopefully you found this useful. Stay tuned for a future tutorial that will teach you some of the more advanced things you can do now that you have your backups routing to your S3 account.

If you’re not already signed up to receive our monthly email update with useful tips like this you can do so in the right margin.