Re: Elastic IP binding with security groups

[Sebastian Stadil]

You can include a security group as a source (e.g., 192.168.2.0/24, sg-47ad482e, or 1234567890/default) if you are simply trying to get app servers to be able to talk to your memcached servers.

Otherwise to create your CNAME, you'll first need to create an A record to your Elastic IP. You can then CNAME that A record.

On Tue, Apr 23, 2013 at 2:01 PM, Sebastian Cabeza <snak...@gmail.com> wrote:

Hi there,

I'm currently setting a memcached server and I assigned a elastic IP to it. The problem is that scalr doesn't give me an endpoint to make a CNAME. And I need to add the endpoint / CNAME (or IP) to the security group of the apps servers to make the connection. How can I do that?

Thanks in advance.

Sebastian.

--
You received this message because you are subscribed to the Google Groups "scalr-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scalr-discus...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Follow us: Twitter - Facebook - Blog

[Nick Toursky]

Sebastian,

Instances within the same EC2 region can connect to each other only using internal IP address.

Regards,

Nick

On Thu, Apr 25, 2013 at 2:39 AM, Sebastian Cabeza <snak...@gmail.com> wrote:

Thanks for replying Sebastian.

The thing is, I added the ports authorization to my Memcached SG to give my Apps servers access. But STILL, no connection... I can connect (ping) through private (local) ip tho... but not to my elastic IP associated to the mem server.

How should the rule of the security group look like?

Thanks in advance for your response!

Regards,

Sebastian C.