How to Back Up Your Server to Amazon S3

Why Amazon S3 Is a Reliable Backup Destination

Amazon S3 offers 99.999999999% (eleven nines) object durability by default — data is automatically replicated across multiple Availability Zones within a region. For backup storage, this means you can treat an S3 object as effectively indestructible under normal failure scenarios. A single AZ failure, server failure, or datacenter fire will not affect your backup data.

Cost-wise, S3 Standard storage is roughly $0.023 per GB per month. A 50 GB backup set costs about $1.15/month in storage — cheaper than most managed backup add-ons. If you use S3 Glacier Instant Retrieval (for archives you rarely access), that drops to $0.004/GB/month.

Create a Dedicated Backup Bucket and IAM User

Never use your root AWS account credentials for backup uploads. Create a dedicated IAM user with the minimum permissions required:

Enable S3 Versioning on the bucket so that overwritten or deleted objects are retained. Enable S3 Lifecycle Rules to transition objects older than 30 days to Glacier and delete objects older than 90 days to manage costs.

Install and Configure AWS CLI on the Server

The Full Backup-to-S3 Script

Schedule the Backup with Cron

CloudStick Manages Offsite Backup Storage Without Extra Config

If you prefer not to manage AWS credentials and S3 lifecycle rules yourself, CloudStick's managed backup storage handles the offsite backup destination — archives are stored in geographically separate managed storage, not on your server. For teams that want explicit control over the destination (e.g., a specific AWS account for compliance reasons), the S3 approach above is the right path to pair alongside CloudStick's dashboard management.