3 ms·

those look just like the other services i looked in to, but w/o diving too deeply in to their whitepapers i can guarantee they use instance/resource tagging as

those look just like the other services i looked in to, but w/o diving too deeply in to their whitepapers i can guarantee they use instance/resource tagging as the shim between AWS and their system(s). with consolidated billing, and a couple of hundred linked accounts (with plenty of turnover), enforcing a sane tagging is pretty much out of the question. thanks for the links tho! when i have a spare few minutes i'll definitely take a closer look.

user5994461 8y ago
Consider revisiting your account strategy. Hundreds of accounts is way too many and it's unmanageable. Even a company with tens of thousands of employees couldn't have anywhere near that. Enforce some tags on purpose, team, business unit, dev or prod. It shouldn't be allowed or possible to create instances without any information. Enforce the rules, if an instance has no information it will be shutdown next week and deleted next month. People will take tagging seriously very soon. I've seen businesses who adopted AWS without any strategy and with revolving contractors as employees. A few months later, it's a hundred instances without a single name or tag, each one costing thousands of dollars a month for the more expensive. If the company cares about costs and resources management, it's easy to achieve. If it doesn't care, then doesn't matter, not your money.