Should Consul instances be placed behind a load balancer
700 views
Skip to first unread message
erich oliphant
unread,
Jun 19, 2017, 2:21:20 PM6/19/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Consul
Hi, I'm working with Consul on AWS and I've been using the ec2 tag support to get the cluster up, clients and servers talking, etc. However, there are still instances where I might need to point directly to a server, say running some scripts that aren't on an EC2 instance, etc. Does it makes sense to just sit them behind an ELB so that there's a well-known address for non-EC2 clients?
James Phillips
unread,
Jun 24, 2017, 7:08:32 PM6/24/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to consu...@googlegroups.com
Hi, in general it's still best to try to run the agent everywhere and
have your applications talk to their local agent. That way if you
register services there you automatically get the serfHealth check for
that agent from the cluster, automatic management of finding a healthy
Consul server, etc. If you can't run an agent then it's ok to run the
ELB (we have some folks that only care about KV, for example, who do
this).