AWS Communism – Part 1: How we cut our Load Balancing cost by more than 96%
1–6 of 6 posts
Re: AWS Communism – Part 1: How we cut our Load Balancing cost by more than 96%
#2Sharing terraform states even across accounts is trivial and easy. The suggested approach seems like a ton of work.
Re: AWS Communism – Part 1: How we cut our Load Balancing cost by more than 96%
#3Sharing terraform states even across accounts is trivial and easy. The suggested approach seems like a ton of work.
But this will only work to share one LB, not scale them automatically
Re: AWS Communism – Part 1: How we cut our Load Balancing cost by more than 96%
#4Re: AWS Communism – Part 1: How we cut our Load Balancing cost by more than 96%
#5Earlier quoted context omitted.
But this will only work to share one LB, not scale them automatically
The `count` operator in HCL wouldn't work?
Within one project: probably.
But it falls apart when sharing stuff between multiple projects. Who's responsible for scaling on demand in that case?
One answer is to solve it within AWS, if you know other solutions that solve the same requirements, be sure to let me know. :)
Re: AWS Communism – Part 1: How we cut our Load Balancing cost by more than 96%
#6Earlier quoted context omitted.
The `count` operator in HCL wouldn't work?
Within one project: probably. But it falls apart when sharing stuff between multiple projects. Who's responsible for scaling on demand in that case? One answer is to solve it within AWS, if you know other solutions that solve the same requirements, be sure to let me know. :)
We solve that by treating shared resources as a separate project.