| ▲ | ajb 3 days ago | |
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. | ||