How can I unpack an old Amazon AMI?
A long time ago, I put together a pretty complex (but quickly built) web app running on an EC2 farm. At some point I abandoned it, and shut down the farm, and I had a copy of the web app code on my local desktop. Before I had a chance to copy it somewhere safe, I had a bad crash, and lost those files. I thought they were gone forever. Recently, I was digging around in my S3 buckets, and found a backup of the Apache AMI I had created on EC2. It consists of a manifest.xml file, and 85 x 10.5MB segments: appname-apache_x64-201103310802.manifest.xml appname-apache_x64-201103310802.part.00 ~ 84 Is there any way to extract the files from this AMI? I've dug around a bit, and I've seen some documentation on ec2-unbundle, but it looks like I might need a private key, and I'm not sure if or where I would still have that (or if I could regenerate it). Perhaps I'm over-thinking it? Any help hugely appreciated! Update: I tried relaunching the AMI as some have suggested. I went into my AWS console, and went to register a new AMI under the EC2 console. When I put in the path to the manifest.xml file (which hasn't moved), I get the following error: HTTP 301 (Moved Permanently) response for URL scalr-images-us-972708971173.s3.amazonaws.com:80/…: check your manifest path is correct and in the correct region. What's weird is that if I copy and paste the URL from the error into a browser (after setting open permissions on the file), the browser downloads the XML file no problem. So why isn't AWS seeing it?
This is what you should do: Launch a micro instance from that AMI (I hope it was registered on your account). Let the setup complete. Login to that instance. Grab the files that you want to your local machine. Kill/terminate this instance. DONE!
Allow HTTP request based on URL and security group
CometD over AWS ELB
How to get JAXRS 2 (Jersey) verbose Trace to work with ResourceConfig
Private docker registry authentication in aws ecs optimized AMI is not successful
Generate swagger json definition for AWS API Gateway
AWS SNS is bypassing API Gateway and calling Lamba functions directly
Access S3 bucket from AWS EC2 via r command lines
Amazon CloudFront and HTTPsL What do I do?
nginx proxy_pass remote ip
SSL Certificates On Elastic Beanstalk Default Setup
Need email open and click events from amazon (aws) ses
Website hosting in specific folder on AWS S3
Opencart images on amazon S3
Programmatically create and deploy On-Demand EC2
How to access S3 bucket from url using boto3?
how to launch ec2 instance using AWS SDK and connect to it via AWS CLI