AUTHOR: http://aws.typepad.com/aws/2011/11/new-aws-elastic-load-balancing-inside-of-a-virtual-private-cloud.html LINK!

Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Webinar: Getting Started on Microsoft Windows With AWS | Main | Amazon CloudFront Update - Fall 2011 »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef0162fcb18d59970d

Listed below are links to weblogs that reference New - AWS Elastic Load Balancing Inside of a Virtual Private Cloud:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

ashley brener

outstanding Jeff.
we're very excited about this.
any indication yet of when multicast support might be added to vpc?

tx
ashley

Mat

Great job. Now hoping that ELB will support paid AMIs soon :)

Mroggen

Jeff, are connections from a VPN into the VPC still precluded from using ELB.

"We are also working on additional enhancements...and the ability to use Elastic Load Balancers for internal application tiers." seems to indicate that isn't supported yet and the diagram doesn't include that scenario either.

Thanks
Mark

Freaky -

We have the same question as Mark. Currently the company security policy dictates that all internet access goes through the main office.

Whilst we can make sure the instances themselves access the internet over the company connection/VPN by the use of the routing tables, this is not the case for incoming traffic through the load balancers, as those require the use of the internet gateway on the Amazon side.

Any information regarding this functionality, especially a timeline, would be greatly appreciated. Projects are currently still in testing phase and it would be nice to know if the functionality is going to be available once we switch to running production.

exprexxo

I wonder what the top layer would look like for using latency based routing?

John

Can you be more specfic about how the pink ELB section is actually created? Everything I have tried gives me the servers of one ELB or the other but not both, i.e. all servers.

Sudarshan Murty

Hi,
You said "In order to allow for room (IP address space) for each ELB to grow as part of the intrinsic ELB scaling process, the subnet must contain at least 100 IP addresses"

What is the genesis of this limit? Rightscale benchmarks of the ELB have monitored 22 IPs in use for a sustained request rate of 19,000/sec ! So what is the reason for requiring a minimum CIDR of /25 ?

thx
sudarshan

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30