 |
Forums |
Admin Discussion Forums: help Start New Thread
| Message: 98002 |
|
BY: JB Koyen (jbkoyen)
DATE: 2012-06-27 17:44
SUBJECT: Issue launching EC2AMI after region migration Hi Guys,
First my congratulations and appreciations for these impressive CS scripts.
I was (am) mainly interested in the EC2 AMI migrations scripts.
And I couldn't (and still can't) believe that Amazon make a EC2 Region migration so hard.
My first attempt to move an AMI from US-east-1 to EU-west-1 was based on NetCat, an approach published by Dotan Mazor.
This approached word flawless, except for a "minor" detail. I wasn't able to launch the AMI in EU-west-1.
Started to launch available AMI's an fiddling and struggling with AKI id's, but it didn't seem to work.
Then I got a tip from a colleague about CloudyScripts.
After creating temporary credentials and a few attempts the copying worked fine.
> Copy AMI To Different Region
> The execution status is: Done (OK)
> Execution Time is: 1706s
Unfortunately I got/kept the same issue as with the NetCat and couldn't launch the AMI.
Maybe I missed some instructions but not the results I had in mind :-(
Unbelievable that or Amazon "friends" make such simple request so difficult.
So back to the kernel tweaks and search for compatible aki id's.
We tested the migration with Oracle Enterprise Linux (OEL 5.6).
Probably not the most popular Linux, but with same roots as Centos: RHEL.
So, back to the basics and followed the step below:
- Create an overview of our own AMI's in us-east-1:
ec2-describe-images --region us-east-1 -oself
- Then an overview of us-east-1 AMI's with the same kernel id's:
ec2-describe-images --region us-east-1 -a | grep aki-xyz
- Now try to find "a good match" in the othe Region based on a description
- So, create a list of AMI's in eu-west-1 and filter on the description
ec2-describe-images --region eu-west-1 -a | grep "AMI description"
- BTW Check not only the aki id's but the ari-id's too
- (re)Register the AMI in the region based on (the earlier created) snapshot
ec2-register --region eu-west-1 -s snap-xyz --kernel aki-eu_located ...
And after registering the snapshots as AMI's, I was (luckily) able to start my instances.
This was actually true for both approaches (CS & NS as well).
My apologies for the long story, the bottom line is: It worked for me.
As earlier stated I really don't understand why Amazon makes it so complicated!?!
The used technique to find an appropriate aki based on an ami description is a bit fuzzy and doesn't feel solid.
Is there a better way to find a corresponding kernel from one region in an other region?
Can you help me out here with the kernel-id question?
Thanks,
JB
| |
Thread View
Post a followup to this message
|
|
Issue launching EC2AMI after region migration