2 ms·

This is the voice of someone who has never actually ended up with a big AWS estate. You don't click to start and stop. You start with someone negotiating credi

by baz00 3y ago

This is the voice of someone who has never actually ended up with a big AWS estate. You don't click to start and stop. You start with someone negotiating credits and reserved instance costs with AWS. Then you have to keep up with spending commitments. Sometimes clicking stop will cost you more than leaving shit running. It gets to the point where $50k a month is indistinguishable from the noise floor of spending.

rewmie 3y ago
> This is the voice of someone who has never actually ended up with a big AWS estate. I worked on a web application that provided by a FANG-like global corporation that is a household name and used by millions of users every day, and which can and did made the news rounds if it experiences issues. It is a high-availability multi-region deployment spread about a dozen independent AWS accounts and managed around the clock by multiple teams. Please tell me more how I "never actually ended up with a big AWS estate." I love how people like you try to shoot down arguments with appeals to authority when you are this clueless about the topic and are this oblivious regarding everyone else's experience.
- baz00 3y ago
  Hey me too.
- dijit 3y ago
  Hrm. I have worked for a global corporation that you have almost certainly heard of. Though it's not super sexy. The parent you're replying to resonates with me. A lot of politics about how you spend and how you commit, it's almost as bad as the commitment terms for bare-metal providers (3,6,12,24month commits). Except the base-load is more expensive. It depends a lot on your load, but for my workloads (which, is fragile dumb but very vertical compute with a wide geographic dispersion), the cost is so high that a few dozen thousand has been missed numerous times, despite having in-house "fin-ops" folks casting their gaze upon our spend.

2 ms·

This is the voice of someone who has never actually ended up with a big AWS estate. You don't click to start and stop. You start with someone negotiating credi

by baz00 3y ago

rewmie 3y ago
> This is the voice of someone who has never actually ended up with a big AWS estate. I worked on a web application that provided by a FANG-like global corporation that is a household name and used by millions of users every day, and which can and did made the news rounds if it experiences issues. It is a high-availability multi-region deployment spread about a dozen independent AWS accounts and managed around the clock by multiple teams. Please tell me more how I "never actually ended up with a big AWS estate." I love how people like you try to shoot down arguments with appeals to authority when you are this clueless about the topic and are this oblivious regarding everyone else's experience.
- baz00 3y ago
  Hey me too.
- dijit 3y ago
  Hrm. I have worked for a global corporation that you have almost certainly heard of. Though it's not super sexy. The parent you're replying to resonates with me. A lot of politics about how you spend and how you commit, it's almost as bad as the commitment terms for bare-metal providers (3,6,12,24month commits). Except the base-load is more expensive. It depends a lot on your load, but for my workloads (which, is fragile dumb but very vertical compute with a wide geographic dispersion), the cost is so high that a few dozen thousand has been missed numerous times, despite having in-house "fin-ops" folks casting their gaze upon our spend.