AWS ELB + ejabberd server

amazon ec2amazon-elbejabberdxmpp

I have two servers in AWS EC2 ejabberd. I'm trying to set up an ELB to manage traffic, but I can not connect when I put a ELB "front" of EC2 instances. DNS settings, I changed the A record for the CNAME public DNS name of the instance ELB.

I read that SRV records can not point to a CNAME, so is not it possible to use ELB + ejabberd?

regards

Best Answer

so is not it possible to use ELB + ejabberd?

It is possible.

XMPP should work via ELB as long as the ELB is configured with a TCP listener instead of HTTP.

You can put the preferred subdomain, a CNAME of the ELB, as the SRV records and that shouldn't be a problem.

This post covers setting up ejabberd behind an ELB: http://overwatering.org/blog/2014/03/straight-forward-clustering-of-ejabberd/

Related Solutions

Amazon EC2 with XMPP infrastructure

You need to point your xmpp hostnames to the EC2 instances, either using CNAME records to Amazon's hostnames:

xmpp1.example.com.  IN  CNAME   ec2-192-0-2-76.us-west-1.compute.amazonaws.com.

or using A records directly to the IP:

xmpp1.example.com.  IN  A   192.0.2.76

The advantage of the CNAME approach is that other EC2 instances looking up the name will resolve to the internal IP. Your SRV records should stay the same as before, and simply point to xmppN.example.com.

If you don't use Elastic IPs the instances will get different IPs each time they are started. If updating DNS every time this happens isn't feasible then you have to use Elastic IPs.

I've never heard of XMPP requiring PTR records to match the forward lookup, this is usually only necessary for SMTP. I've run XMPP servers where this hasn't been the case and haven't had any problems. If you really want this, Amazon do let you configure reverse lookups for Elastic IPs, but this is intended for mail servers and so you may need to convince them that you need this.

How to forward godaddy domain to ec2 load balancer

You can't.

ELB provides one -- or more -- IP addresses, hiding behind the CNAME you are using with www record, and these addresses are not static, so you can't create an A record at the top ("apex") of your domain and point to the addresses... along with that, a CNAME at the apex of a domain is not a valid DNS configuration. So there isn't directly a way to do this.

You can either use Go Daddy's web site forwarding feature to redirect example.com requests to www.example.com, which will cause the browser to change its address bar value from example.com to www.example.com and then send traffic to the ELB (via the www CNAME)... or you can move the DNS from Go Daddy to Amazon's Route 53 service, which has another feature that operates similarly to a CNAME but is implemented differently, consistent with the rules established in RFC-1912. They call these ALIAS records.

An Alias record in Route 53 is a pointer to internal configuration within Route 53 that allows that service to look up and return an appropriate A-record for the service to which the Alias record is pointing.

http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/CreatingAliasRRSets.html

Best Answer

Related Solutions

Amazon EC2 with XMPP infrastructure

How to forward godaddy domain to ec2 load balancer

Related Topic