The instance we booted was assigned the default security group. Edits made to a security group are immediately applied to the instances operating in them. We just added the ping and SSH rules to allow incoming traffic to the instances running in the default security group, so you should be able to ping and SSH to the instance you launched. Here's the output summary:
laptop# ping -c 3 192.168.122.3 PING 192.168.122.3 56(84) bytes of data. 64 bytes from 192.168.122.3: icmp_seq=1 ttl=64 time=0.040 ms 64 bytes from 192.168.122.3: icmp_seq=2 ttl=64 time=0.041 ms 64 bytes from 192.168.122.3: icmp_seq=3 ttl=64 time=0.040 ms --- 192.168.122.3 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.040/0.040/0.041/0.005 ms laptop# ssh [email protected] The authenticity of host '' 192.168.122.3 (192.168.122.3)'' can''t be established. RSA key fingerprint is 83:d8:f4:7e:01:db:4e:50:8a:bd:f6:dc:77...