Amazon ELB cost reduction

[hazim1093]

Research on how we can reduce the infrastructure cost of ELBs

[hamza3202]

The breakdown of ELBs is as follows:

1- The Core stack a- We have 1 ELB each for registry, gocd and etcd. b- We have 2 ELBs (external and internal for fleet) for admiral (which will host applications that maybe needed by the core application. e.g MySQL. c- Currently we have 1 elb for MySQL which will soon be moved to admiral once its completed 2- The Cluster Environment We have 2 ELBs (internal and external) for worker instances 3- The Blue Green Environment We have 2 ELBs (active and test) for each environment of each application

[hamza3202]

Refer to this document for graphical analysis https://github.com/stakater/documentation/blob/master/Infrastructure/Stakater%20-%20Infrastructure%20Overview.svg

[rasheedamir]

Regarding ELB's this shld be our goal:

1) For infrastructure components we don't necessarily need any ELB. We can make it optional and by default we shouldn't have one. 2) For non public facing production apps we shld use interanal soft loadbalancing using nginx or haproxy; or best to have client side load balancing. 3) For production public facing apps it shld be MUST to have an ELB.

One question though: what about the worker & admiral clusters; is it mandatory to have infront of them?

[rasheedamir]

Also we need to keep in mind our goal is to minimally use those services of a cloud provider which can lock us.

[rasheedamir]

@hazim1093 @hamza3202 i think this needs to be solved alongwith #5 & #42 They seem to be duplicate.