[jpr5]

Really digging this product so far. So many times I've set up complicated multi-region service architectures in AWS and will still struggle to produce simple POVs on cost consumption (and credit usage/outlook, for all us startups).

This thing is pretty damn straightforward and simple (which is good), and TIL from Vantage that I've been using the wrong volume type - gp3 is better and would save me money. I feel dumb not knowing, but now Vantage made me a little smarter. ;-) Three cheers for the cost savings recommendations!

[clipradiowallet]

To be honest, this is all the domain of your AWS service advisor. At any type of scale(eg, when you move to invoiced billing because CC billing would be absurd), you should be overwhelmed by phone calls from that individual. While half of their job is to upsell you, the other half is to help you save costs to garner goodwill(and your future business).

If you've been dodging these calls in the past, it might be worth picking up the phone.

[nijave]

I've heard of some latency issues with gp3 vs gp2--not sure if that's been resolved. Of course, services like RDS don't support it yet, either (same with io2)

As for cost consumption, splitting services into separate AWS accounts (even per-environment) helps if they're large (plus then you're less likely to hit rate limits, worry about IAM segregation, etc)

[Pokepokalypse]

I just did a mass conversion of gp2 to gp3. gp3 DOES increase disk latency, but we're talking 2ms -> 4ms. So it's doubled, but still pretty low. For normal usage, it's still quite fast.

[Thristle]

You shouldn't feel too bad, most companies/people don't know how much money they are wasting on AWS.

Moreover, gp3 is very new (in cloud time) and most people don't use it since it's not really supported that well in cloudformation