• carl_dungeon@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I regularly support clients where reserved instances, compliance, and auto scaling by themselves translate into millions of dollars of annual savings over on-prem.

    Our biggest data storage client has over 7PB of s3 and has legally obligated retention and destruction policies. Spread across about 100 different projects, having central management of that alone saves probably $100k a month in auditing, class transitioning, purging, and inventory just in man hours.

    I oversee one client with over 200 aws accounts in their org, and I’m able to do it solo- in the 90s that involved dozens of people to support the hardware and networks alone.

    You’re not wrong that orgs can do it badly and don’t understand how to leverage services, but that also doesn’t mean it can’t be done well. You know how much a NIST 800-53 ATO costs in labor hours alone in a large org? It’s $$$. Cloud tooling automated so much of that and largely eliminates all the hardware and physical control components entirely.

    Plus when you consider govcloud and fedramp, that’s stupidly hard to do on your own, but with cloud you get those things as built-ins.

    • fuser@quex.ccOPM
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      For auto-scaling to realize material savings, the variation in the workload needs to represent a significant change in the production footprint. Many applications in the Private Sector now being dumped into relatively expensive compute and storage cloud services don’t have that profile. A handful of virtual servers inside a corporate data center with an internal user base is usually uneconomical to refactor or replace with a lower-cost footprint, at least for now.