Yeah that. We moved to AWS using their best practices and enterprise cost estimation stuff and got a 6x cost increment on something that was supposed to be cheaper and now we’re fucked because we can’t get out.

It’s nearly impossible to tell what the hell is going where and we are mostly surviving on enterprise discounts from negotiations.

The worst thing is they worked out you can blend costs in using AWS marketplace without having to raise due diligence on a new vendor or PO. So up it goes even more.

Not my department or funeral fortunately. Our AWS account is about $15 a month.

▲

ajb 3 days ago | parent | next [-]

Are you using separate accounts per use case? That's the only real way to get a cost breakdown, otherwise you have no idea what piece of infrastructure is for what. They provide a tagging system but it's only informative if someone spends several hours a month tracking down the stuff that didn't get tagged properly.

	▲	bumblehean 3 days ago \| parent \| next [-]
		> They provide a tagging system but it's only informative if someone spends several hours a month tracking down the stuff that didn't get tagged properly. The way to deal with this is with an org-level Service Control Policy that enforces the tagging standards. A resource doesn't have the right tags associated with it? It can't be created. https://docs.aws.amazon.com/organizations/latest/userguide/o...
	▲	crinkly 3 days ago \| parent \| prev [-]
		Yeah we have many accounts. Hence why I know ours cheap. Difficult to break it down within the account as you say without tag maintenance.

▲

AtheistOfFail 3 days ago | parent | prev | next [-]

> The worst thing is they worked out you can blend costs in using AWS marketplace without having to raise due diligence on a new vendor or PO. So up it goes even more.

Not a bug, a feature.

▲

bufferoverflow 3 days ago | parent | prev [-]

[dead]