I'm trying to open up the MySQL (3306) port on my EC2 instance and even though I've added the rule, it appears the port is still closed. Do I need to reboot my instance for the policy changes to take effect?
on 10/27/2012 – Made popular on 10/27/2012
So I've done this a few dozen times on a 'normal' box (not in EC2) and it seems simple enough. I was trying to run ssh on port 22 and 80 but I couldn't, for the life of me, figure out why I can't connect through port 80 but I can connect fine using port 22.
I have created an EC2 Security Group that allows incoming traffic from a private ip address in the same account.
It is my understanding that a private ip address for a classic instance can change after reboot.
My app has several AsyncTaskRunners which are constantly access the database. I keep getting ThreadPool errors because of a closed database instance. Originally I had a new instance opened and then closed again, each with a different name every time.
I have not changed the security settings on my Amazon EC2 m1.small instance, but ever since I recently installed security updates, including a new kernel, it stopped accepting new ICMP echo and tcp connections to ports other than 22.