<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap:break-word"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <br> <div id="bloop_sign_1494195459462490112" class="bloop_sign"></div> <br><p class="airmail_on">On May 5, 2017 at 14:17:46, Rick Hornsby (<a href="mailto:richardjhornsby@gmail.com">richardjhornsby@gmail.com</a>) wrote:</p> <div><blockquote type="cite" class="clean_bq" style="font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span><div style="word-wrap:break-word"><div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><br class="Apple-interchange-newline">Has anyone tried to import a CentOS virtualbox VM into aws/ec2?</div></div></div></span></blockquote></div><p>I think I finally figured it out. I think there were a couple of issues that maybe I resolved along the way, but the biggest one that was keeping cloud-init from running correctly in the end is that I copied the contents of cloud.cfg from the elastic guide[1], but didn't realize I copied the closing 'EOF' into the file as well. That doesn't belong.</p><p>I wish that the elastic guide didn't have such a gaping hole in the instructions. Actually, I wish somewhere something explained that there are no cloud-init commands that need to be run manually on the local side to set anything up. cloud-init just needs to be installed via yum, apt etc and have the configuration file set. The cloud provider system (ie ec2) handles the rest.</p><p>[1] <a href="https://www.elastic.co/blog/create-an-ami-from-your-own-vm-image">https://www.elastic.co/blog/create-an-ami-from-your-own-vm-image</a></p></body></html>