Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cost Optimization Best Practices from Trend Micro

943 views

Published on

Cliff Lu talked about how Trend Micro saved cost on AWS. Presented on AWS re:Invent re:Cap in Taipei, Enterprise track, Dec. 1st, 2015.

Note: I'll revise the slides and add more notes so it's easier to read.

Published in: Software
  • Be the first to comment

Cost Optimization Best Practices from Trend Micro

  1. 1. © 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Cliff Chao-kuan Lu, DCS, Trend Micro Dec. 1st, 2015 Cost Optimization Best Practices from Trend Micro
  2. 2. Cliff Chao-kuan Lu 呂昭寬 • Trend Micro Inc., DCS, AWS-PS • AWS User Group in Taiwan • Full-stack Web Developer • Certified Pro-Level AWS SA
  3. 3. Trend Micro Inc. • Leader in IT security • Advanced technology partner since 2012 • DCS became consulting partner 2015 • 200+ AWS accounts from 50+ service teams
  4. 4. Consolidated Billing • Share reserved resources • Volume discount • Enterprise support
  5. 5. Reviewing our Bills
  6. 6. Cloud is the New Normal • 10x growth in 2 ½ years • RI on Q1 every year (%) 0 20 40 60 80 100 120 2013-02 2013-05 2013-08 2013-11 2014-02 2014-05 2014-08 2014-11 2015-02 2015-05 2015-08
  7. 7. Reserved Instances • Used to be part of budget execution • Rolled out Moneyman for central management 2015-03 (%) 0 10 20 30 40 50 60 70 80 90 100 2013-07 2013-10 2014-01 2014-04 2014-07 2014-10 2015-01 2015-04
  8. 8. Cost Fraction by Category • %EC2 dropped from 80% to 60% • 16% increase for managed services (%) 0 10 20 30 40 50 60 70 80 90 100 2013-02 2013-05 2013-08 2013-11 2014-02 2014-05 2014-08 2014-11 2015-02 2015-05 2015-08 EC2 EC2Based PaaS Others
  9. 9. Get `Cloudy` • Budgeted service migrated to AWS in 2015 • Replace Mogile FS with S3 • 20% cost saving from elasticity and capacity in the cloud • Better data durability
  10. 10. Re-Architecture • Log-stream buffering service • Node.js, Redis, and MongoDB on EC2 • Recommended API Gateway, Lambda, and Kinesis • Saves 50% running cost • Improved availability and scalability
  11. 11. Or, Not to Re-Architecture • Footprint: 100 Windows servers, 4 stages • Planning migration to AWS in 2016 • Lift and shift • ~20% Cost reduction compared to on-premises designed 5+ years ago • Another 20% allocating stacks only when needed
  12. 12. Key Takeaway • There’s no lock-in • Managed services are performant and low cost • Stop or free unused resources • Reserved resources for baseline load and save more
  13. 13. Thank you!

×