FOOD FOR THOUGHT Mayday! Mayday!

[billsimon]

When you bring up the new instance, attach the PIAF disk at device /dev/xvdb or /dev/sdb (I forget but the EC2 console will make it clear). Then when you boot up your new temporary instance, log in to it over SSH. Become root and issue

mount /dev/sdb /mnt

Then your PIAF disk is available at /mnt. Now cd to /mnt/etc and look in the rc#.d directories for files matching "S##iptables". Those are the symlinks that tell the OS to start (the "S") the service, and the number is the order in which it starts. Remove those S##iptables symlinks so that iptables won't start at boot. I believe CentOS starts at runlevel 3 normally, so you definitely want to clear the S##iptables out of rc3.d but might as well remove them from the other runlevels too.

You could also edit the /mnt/etc/sysconfig/iptables file to let yourself in. I'd recommend just turning off iptables on EC2 and using the Security Groups firewall system. You'll likely get differing opinions on this.

When done editing the PIAF disk, cd / and umount /mnt and then shutdown the temp instance, put the volume back on the PIAF instance, boot up, and see how it goes!

 

[JohnACE13]

Thank you all for your help, but I couldn't get it done... Long story short, I ended up starting from scratch. The good thing is I am up and running again, but for some reason I have a new issue....

When I attempt to SSH to my ec2 instance the server is refusing my key. I went through the same steps I did the first time (creating a key in AWS, exporting it and using puttygen to convert the file) but I can not gain access. Does anyone have any idea what the problem could be and should I start this in a new thread?

 

[Mark D. Montgomery II]

Did you upload your home key back to the ec2 instance? (Don't know how those work, so I don't know if it's the same process as a normal Linux server)