Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have multiple short-term projects for different clients that run on separate EC2 instances, some using databases on RDS and all running from GitHub repos. Once a project is done, what's the best way (cost, organization) to archive everything? Just take snapshots and terminate everything? If so, should the snapshots be stored anywhere specific? I've heard about Glacier but I don't think believe it's for snapshot storage...

Your advice is appreciated.

share|improve this question

1 Answer 1

up vote 0 down vote accepted

Once a project is done, what's the best way (cost, organization) to archive everything? If your code is sitting in GitHub you may not have anything on the EC2 that you care to archive.

If you do have some data to archive (on your EC2) you can zip it up and send it to AWS S3, or better still AWS Glacier.

If you're interested in storing a complete copy of the EC2 you can use the AWS EC2 Snapshot feature (this stores data in S3 for you, but you don't have direct access to the bucket).

RDS is a similar situation. You could backup your data and send it to S3/Glacier, or you could use the Snapshot feature.

I've heard about Glacier but I don't think believe it's for snapshot storage...

Glacier can store your own data but you cannot choose where EC2/RDS snapshots live.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.