Amazon EC2 instance missing Network Interface
- by Sergiks
I am running Linux on a t1.micro instance at Amazon EC2.
Once I noticed bruteforce ssh login attemtps from a certain IP, after litle Googling I issued the two following commands (other ip):
iptables -A INPUT -s 202.54.20.22 -j DROP
iptables -A OUTPUT -d 202.54.20.22 -j DROP
Either this, or maybe some other actions like yum upgrade perhaps, caused the follwing fiasco: after rebooting the server, it came up without the Network Interface!
I only can connect to it through AWS Management Console JAVA ssh client - via local 10.x.x.x address.
Console's Attach Network Interface as well as Detach.. are greyed out for this instance.
Network Interfaces item at the left does not offer any Subnets to choose from, to create a new N.I.
Please advice, how can I recreate a Network Interface for the instance?
Upd. The instance is not accessible from outside: cannot be pinged, SSH'ed or connected by HTTP on port 80.
Here's the ifconfig output:
eth0 Link encap:Ethernet HWaddr 12:31:39:0A:5E:06
inet addr:10.211.93.240 Bcast:10.211.93.255 Mask:255.255.255.0
inet6 addr: fe80::1031:39ff:fe0a:5e06/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1426 errors:0 dropped:0 overruns:0 frame:0
TX packets:1371 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:152085 (148.5 KiB) TX bytes:208852 (203.9 KiB)
Interrupt:25
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
What is also unusual: a new micro instance I created from scratch, with no relation to the troubled one, was not pingable too.