Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using the following Amazon EC2 resources in the US East (Virginia) region:

  1. 1 Running Instance
  2. 1 Elastic IP
  3. 2 EBS Volumes
  4. 100 EBS Snapshots
  5. 1 Key Pair
  6. 2 Security Groups
  7. 5 My Own AMIs (customized based on my application stack)

My instance is based on Linux distribution (CentOS) and my AMIs are S3-backed. Both EBS volumes are mounted on this running instance.

We're planning to migrate our deployment to US-West region. Because Amazon EC2 resources are not shared across regions, my questions are:

  1. What are all the factors that I need to consider in advance?
  2. What are all the recommended & different ways of migrating each EC2 resources from one region to the other?
  3. Are there any hidden risks involved during and/or after the migration?

Experts ideas/suggestions/recommendations on this are highly appreciated.

share|improve this question

We run AMIs in three regions. The key point is that regions are completely separated, so you will have to move everything to other regions (via S3) and recreate your security groups etc.

For the move itself, Elastifox is a great help:

It is more powerful then the Web interface and helps with moving AMIs.

Potential problems that we encountered:

  • Moving AMIs (the copying) can take hours! So plan enough time for this.

  • Sometimes we had problems registering the AMI or it arrived corrupted. I am not really sure what caused these issues, but we could always solve them (in the worst case we had to copy the AMI again - did I mention to plan enough time ;)

share|improve this answer
That an interesting problem with the AMI. What was Amazon's response to that? – Rob Olmos Oct 30 '10 at 20:22
Thanks for sharing your experience here. BTW, "Migrate AMI and Register" option is disabled against my own AMI. How do I enable this option? – Gnanam Nov 1 '10 at 9:08
Currently, ElasticFox only allows for migration of Windows AMIs, not Linux AMIs. You can check here: – Gnanam Nov 2 '10 at 13:34

We are using own Python package django-fabfile (based on boto and Fabric) for replicating several tens of production Ubuntu instances into backup region. Snapshots are updated daily in backup regions. In case if instances should be restored in backup region new AMI could be created and launched in few moments.

share|improve this answer

Your Answer


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.