From www to elastic LB

[Jhb]

Hi,

Can you please provide simple steps to use the elastic LB ?

I'm running a classic www-app-mysql farm, and would like to remove the
www role and benefit from the elastic LB (cheaper).

Thanks for your help,

Jonathan

[Arie Fishler]

I saw that on the farm edit window there is a load-balancing tab where you can select an elastic-lb on the instances of a specific role. I guess that once you select it you can give up using the www role

my following question - is there any replacement for the "not available" messages that were customized on the www role? I replaced the 50x.html pages with my own...

What's the behavior of the elastic LB when nothing is available behind it?

[Nickolas Toursky]

Hi,

To use Elastic LB, you should:

1. Remove www role from the farm.
2. On the farm edit page, enable 'Use Elastic Load Balancer' option
for app role ('Load Balancers' tab).
3. Add ports 80 and 443 as listeners.

All the new instances of this role will be automatically registered on
the Load balancer.

Next, add a DNS record 'www IN CNAME LoadBalancerHost' for your
application. LoadBalancerHost is available on Farms->Elastic Load
Balancers page.

Nick

[Nickolas Toursky]

Hi Arie,

Unfortunately, Amazon does not provide an ability to override HTTP
error handlers.

Nick

On Mon, Jun 29, 2009 at 3:55 PM, Arie Fishler<afis...@gmail.com> wrote:

[Arie Fishler]

thanks Nick.

[Jhb]

Thanks. Do you recommend using the elastic LB vs the www role ?

[Arie Fishler]

Nick,

another question on the LB. If I start a farm that has one app role and I assign it the www CNAME without the elastic LB will I have any problem changing it when I scale to multiple instances and need to reassign the www CNAME to the load balancer? I remembe there was some issue in the past with modifying DNS records. Don't know if this is still relevant.

[Arie Fishler]

anyone?

[Nickolas Toursky]

Arie,

Not sure what problem you are talking about, but for now there are no
known issues with DNS records.
In general, there should be no problem with doing as you wish, but of
course I'd recommend you to test it first.

Nick

[Colin Howe]

Is there a way to do this without removing the www role?

I'd like to add the load balancer and have the www role still running
- so that I can test the load balancer is working before potentially
destroying our production site :-)

Cheers,
Colin

On Jun 29, 3:20 pm, Nickolas Toursky <hin...@gmail.com> wrote:
> Hi,
>
> To use Elastic LB, you should:
>
> 1. Remove www role from the farm.
> 2. On the farm edit page, enable 'Use Elastic Load Balancer' option
> for app role ('Load Balancers' tab).
> 3. Add ports 80 and 443 as listeners.
>
> All the new instances of this role will be automatically registered on
> the Load balancer.
>
> Next, add a DNS record 'www IN CNAME LoadBalancerHost' for your
> application. LoadBalancerHost is available on Farms->Elastic Load
> Balancers page.
>
> Nick
>
>
>
> On Mon, Jun 29, 2009 at 3:55 PM, Arie Fishler<afish...@gmail.com> wrote:
> > I saw that on the farm edit window there is a load-balancing tab where you
> > can select an elastic-lb on the instances of a specific role. I guess that
> > once you select it you can give up using the www role
>
> > my following question - is there any replacement for the "not available"
> > messages that were customized on the www role? I replaced the 50x.html pages
> > with my own...
>
> > What's the behavior of the elastic LB when nothing is available behind it?
>

[Nickolas Toursky]

Hi Colin,

Of course it is not mandatory to disable www role.

After enabling 'Use Elastic Load balancer' option for app role use
load balancer's hostname to test it.

Nick

2009/7/7 Colin Howe <colint...@googlemail.com>: