[solatic]

> it is not allowed due to billing reasons. Company policy is: One product per AWS account.

That's kinda funny because half the reason why AWS has tags in the first place is to get finer granularity into understanding billing. Not to mention products like Kubecost. Sounds like whoever wrote the policy doesn't understand how AWS works.

> Someone needs to do the dirty work but nobody wants to do it.

There are plenty of people willing to do the dirty work, they're just already working for other companies and their salaries are quite high. The labor market is tight.

> Cui bono? Neither our team, nor our users nor our infrastructure bill.

HR benefits. Having open positions that HR is failing to fill is a bad look for HR.

[adgud]

Not everything can be tagged to get the source of the cost - for example I don't think you can differentiate which of your products generated egress network traffic (which is quite costly as soon as you reach certain scale). I might be wrong, I switched to separate-account-per-product a while back and never looked back.