Hacker News Reader

keep in mind, AWS best practices (and IAM limitations, for those without resources/time to finely craft the boundaries) encourage account sprawl...

Not all customers spread out like we do... but I manage over 50 AWS accounts, and our DevOps team is 7 FTE... Our application/situation is admittedly unusual, but I could easily see a small business using 10 accounts to manage their org and a single "product"

View on HN

I used to be a consultant building exactly those designs, limit the blast radius, have separate accounts etc.

"In the earlier days" of ARGOS that's exactly why I didn't charge per Account, but different ways (tried # of resources, then % of spend) and people were always confused.

Similar to the "take the price off the website" that customers told me, me charging per Account is also what customers asked me to do.

What do you think would a good unit be for a product like this? I'm happy to try anything really, as long as it helps companies be more secure.

Reply on news.ycombinator.com