How to use Resource Rightsizing

Rightsizing is one of the best ways to bring cloud costs under control. You have to analyze instance performance and usage patterns and needs continuously. After that, turn off idle instances and rightsize any instances that are either poorly matched to the workloads or overprovisioned.

Rightsizing is an ongoing process. Resource needs are constantly changing, and you need to achieve cost optimization. Make rightsizing a process that is as hurdle-free as possible. Third-party AWS tools, such as nOps, will simplify resource analysis and monitoring.

Review Amazon Cloudwatch metrics to identify usage patterns and needs that enable you to take advantage of rightsizing opportunities.

  • Steady State: In the steady state, the load remains at a constant level for some time. It is even possible to forecast the compute load at any one time. For this type of usage pattern, consider Reserved Instances. They can yield significant savings.

  • Variable and predictable: For such instances, the load varies over time but on a predictable schedule. AWS Auto Scaling is ideal for applications that exhibit stable demand patterns weekly, daily or hourly usage variability. You can use AWS Auto Scaling to scale EC2 capacity whenever there is a spike or fluctuation in traffic.

  • Dev/test/production: Turn off production, testing, and development environments in the evening since organizations usually use them during business hours.

  • Temporary: Do you have temporary workloads with flexible starting times that you can interrupt? Avoid using an on-demand instance. Instead, place a bid on an Amazon EC2 Spot Instance.

Click on Cost Control

Select Resource Rightsizing

Use the tabs at the top to switch between EC2, RDS, and S3

Use the Filters section to look through specific information on:

  • AWS Account

  • Instance Types

  • CloudFormation: StackName

  • Autoscaling Group

  • Regions

  • Tags

Using the columns Current Config and Suggested Config uses data over the past 2 weeks to make the suggestion of downsizing.

Click on Resource Details to look at Resource Details, Cost History, and Configuration History

Did this answer your question?