[chef] Re: Re: Re: Re: Re: Attach an ec2 instance on the existing ELB

[nick hatch < >]

On Tue, May 28, 2013 at 9:16 AM, Chandan Maheshwari < " target="_blank"> > wrote:

Is there any other way of doing this.

Yes -- consider not doing it at all.  While there may be valid reasons for taking this approach, I think it might be worthwhile to reevaluate the problem and see if you really need to use chef to manage your ELBs.

An alternative is to associate the ELB with the AS group, so that nodes automatically register. Use a robust health check @ the ELB so that nodes aren't routed traffic unless they can serve the requests successfully. (You'll want a good health check anyways so when things go bump in the cloud, unhealthy nodes aren't attempting to serve requests. )

I've had tens of thousands of instances go through this life-cycle and it works quite well.

AWS's tooling here is good and battle-tested. It seems that Chef's might not be. If it hurts to use your configuration management framework to manage your ELBs, perhaps you shouldn't do that.

There's also probably an argument to be made that introducing Chef as an actor in AS/ELB introduces some complexity around fate sharing that can be problematic if not done carefully.

-n