Right-sizing best practices for Amazon EC2

Right-sizing best practices for Amazon EC2

  1. Start simple: uses idle resources, not important in product development and QA. Virtual machines will require less test time.
  2. Right Size before performing a migration: If the appropriate size is ignored to save time, the transmission speed may decrease, it may increase the transmission speed but will increase the cost. Therefore, it is advisable to take advantage of the test and QA cycle during the transfer to test several virtual machines.
  3. The best right sizing starts on day 1: When doing a proper sizing analysis and determining the right size for a resource, make sure all knowledge is shared within the organization and influence the design of new workloads.
  4. Measure Twice, Cut Once: Test, then test some more: Test to determine if the desired resource is working correctly.
  5. Test once and perform multiple right sizing: Aggregate cases for each auto-sizing group and tags to scale the sizing operations accordingly
  6. Combine Reserved Instance or Savings Plans strategy with Right Sizing to maximize savings
  7. Ignore burstable instance families (T types): These families are typically designed to run at low CPU percentages for a significant amount of time and should not be part of the current virtual machine classes. analyzed for permissions.