nOps provides several forms of cost optimization recommendations ranging from unused, underutilized, and infrequently accessed resources to resource rightsizing recommendations.
In the nOps platform, you can find cost optimization recommendations on the:
Rules > Cost tab:
Cost > Resource Rightsizing page:
nOps Rules Cost Recommendation
The cost optimization recommendations in the Rules > Cost tab provides cost optimization recommendations with details of the appropriate step you can take.
Following is a list of cost optimization recommendations that nOps provides in the Cost page. The list is not exhaustive, nOps is constantly adding more recommendations that will help you reduce costs:
Unused AWS EBS Volumes
Unused AWS Elastic IP (EIP) Resources
Unused AWS NAT Resources
Unused Azure Disk Storage
Unused Azure Network Interfaces
Unused Azure Public IP Addresses
Unused Azure Virtual Machine
Unused Azure Virtual Network NAT
Underutilized AWS CloudWatch Log Group
Underutilized AWS EBS Provisioned IOPS
Underutilized AWS ELB Resources
Underutilized AWS RDS Provisioned IOPS
Underutilized (% read/write) CosmosDB Containers
Underutilized (% read/write) DynamoDB Tables
Underutilized (%) ECS Cluster
Underutilized (% capacity) EC2 Instances
Underutilized Azure Virtual Machine
Infrequently Accessed AWS S3 Bucket
Infrequently Accessed Azure Storage Account Buckets
Infrequently Accessed Azure Storage Account Resources
Review EC2 Instances (low traffic)
Review EC2 Instance Size
Review S3 Storage Class
Review MySQL Instance Size
Review Azure MariaDB Instance Size
Review Azure PostgreSQL Instance Size
Disabled Autoscaling CosmosDB Containers or Databases
Disabled Autoscaling DynamoDB Tables
Unattached Workspace Directory
Resource Rightsizing Recommendations
Rightsizing is one of the best methods to bring cloud costs under control. nOps provides resource rightsizing recommendations for these AWS services:
Each service has its own dedicated tab with recommendations:
To reduce costs by rightsizing, nOps allows you to analyze instance performance, usage patterns and needs continuously. nOps then provides cost optimization recommendations to turn off idle instances and to rightsize instances that are either poorly matched to the workloads or over-provisioned.
On the Resource Rightsizing page, against each resource, nOps provides:
Current Monthly Cost
New Monthly Cost (If the Suggested Configuration is implemented)
Rightsizing is an ongoing process since resource needs are constantly changing. nOps simplifies both resource analysis and monitoring, which enables you to make rightsizing a regular part of your cloud management process.
nOps analyzes your resourse and provides cost optimization recommendations based on the state and usage of resources. nOps categorizes the resources and recommendations based on these states:
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.
The nOps Process
The recommendations of nOps are based on a rigorous process that is often unique for each form of recommendation.
Following are examples of how nOps comes to the conclusion that rightsizing is required and offers you the recommendation to act upon.
Let’s say you have an AWS EKS instances that is m6i.xlarge, nOps looks at no less than 23 different metrics and concludes the right size of the instance according to your current need:
Please update the instance type to m5d.2xlarge
In this case, nOps recommends that you update your instance from m6i.xlarge to m5d.2xlarge.
If you have CloudWatch enabled, nOps will collect 6 key metrics for every CloudWatch enabled EC2 instance in your environment:
For each instance in your environment, nOps will make the following calculations:
Harmonic mean of disk read and write
Disk read and write averages
Average network in / out utilization to six points of precision
Average memory utilization
Average CPU utilization
nOps continuously monitors a 30 day sample of your utilization data and matches your CPU requirements to the latest offerings in the AWS pricing catalog in order to select the best match for your resource requirements.
If you don’t have CloudWatch enabled, nOps will still recommend the latest offering upgrades for your given instance class, when they are available.