EC2 from the security group does not work - what did I do wrong?

Question

I have two instances.

IOne is in us-east-1b and is in the bamboo security group

ITwo is in us-east-1c and is in the ssh security group from bamboo

In ssh from bamboo, I allow incoming traffic to port 22 from the 'bamboo' group

As a result, IOne gets timeouts when trying SSH in ITwo

If I change the security rule to the IOne IP address instead of the group name, the SSH connection will succeed.

I read that both cars should be in the same region (although the zones are not mentioned in it). Should my installation work? If not, what do I need to change?

Answer 1

You cannot use a public IP address, but you can use a public host name (ec2-IPADDRESS-.us-east-1.compute.amazonaws.com) because it will allow an internal IP address when called from within EC2, and will allow an external IP address from outside the Amazon network.

Answer 2

This answer may be late, but @datasage was probably right. You need to use your IP address, not public or Elastic IP

From AWS EC2 Documentation :

Inbound traffic is allowed based on the private IP addresses of the instances that are associated with the original security group (and not the public IP address or Elastic IP addresses).