Right-Size Reporting
Right-size reports are monthly reports that provide customers cost optimization recommendations based on automated checks that are evaluated on a weekly basis - providing tenants with an actionable list of potential waste within their cloud deployments. In addition to your monthly report, customers will be provided a folder on Google Drive that will contain previous reports for your needs. Below you will find an example right-size report, a summary of how to interpret the report, and a detailed description of the checks and potential actions associated.
Interpreting the Report
The Summary tab is the only tab that will always exist. Additional tabs are dynamically added based on your account assessments. On the Summary tab you will find a Summary of Checks and a Summary of Accounts.
-
The Summary of Checks provides the aggregate potential savings for each check type in the report.
-
The Summary of Accounts provides the potential savings per account associated with your customer profile.
Each dynamic tab will display each cloud resource that was identified by the corresponding check and the potential monthly savings that would be realized by eliminating that resource entirely.
Potential Savings are based on removing resources entirely from the account. Ideally when appropriately sized you should be able to achieve 60-80% of this potential savings
Example Right-Size Report
Below is an example of the report that you will be provided on a monthly basis.
Checks and Actions
Checks have predefined metrics and measures that qualify a particular cloud resource as potentially being underutilized or wasteful of cloud spend. These are not adjustable but should provide product owners and teams with a quickly actionable list of cloud spend optimization opportunities.
Below you will find a description of each check and the corresponding potential actions available to you. Each check is evaluated on a weekly basis and may contain cloud resources that have already been decommissioned.
Low Utilization Amazon EC2 Instances
Description
-
Checks the Amazon Elastic Compute Cloud (Amazon EC2) instances that were running at any time during the last 14 days. This check alerts you if the daily CPU utilization was 10% or less and network I/O was 5 MB or less for at least 4 days.
-
Running instances generate hourly usage charges. Although some scenarios can result in low utilization by design, you can often lower your costs by managing the number and size of your instances.
-
Estimated monthly savings are calculated by using the current usage rate for On-Demand Instances and the estimated number of days the instance might be underutilized.
Actions
-
Terminate unneeded instances
-
Downsize underutilized instances
-
Turn off instances when not required (non-production)
Underutilized Amazon EBS Volumes
Description
-
Checks Amazon Elastic Block Store (Amazon EBS) volume configurations and warns when volumes appear to be underutilized.
-
Charges begin when a volume is created. If a volume remains unattached or has very low write activity (excluding boot volumes) for a period of time, the volume is underutilized.
Actions
-
Delete unneeded EBS Volumes
-
Reduce the EBS Volume size
-
Consider using an S3 bucket
AWS Lambda Functions with Excessive Timeouts
Description
-
Checks for Lambda functions with high timeout rates that might result in high cost.
-
Lambda charges based on run time and number of requests for your function. Function timeouts result in errors that may cause retries. Retrying functions will incur additional request and run time charges.
Actions
-
Delete the Lambda Function
-
Adjust the Lambda Function timeout to the maximum of 15 minutes
-
Refactor the Lambda Function to operate within 15 minutes
-
Refactor the Lambda Function to process in parallel/recursive executions
-
Refactor the Lambda Function to process batches
-
Consider AWS Batch for tasks that require more time
AWS Lambda Functions with High Error Rates
Description
-
Checks for Lambda functions with high error rates that might result in higher costs.
-
Lambda charges are based on the number of requests and aggregate run time for your function. Function errors may cause retries that incur additional charges.
Actions
-
Delete the Lambda Function
-
Identify and resolve the root cause
-
Refactor the Lambda Function to handle errors more gracefully
Idle Load Balancers
Description
-
Checks your Elastic Load Balancing configuration for load balancers that are idle.
-
Any load balancer that is configured accrues charges. If a load balancer has no associated backend instances, or if network traffic is severely limited, the load balancer is not being used effectively.
-
This check currently only checks for Classic Load Balancer type within ELB service. It does not include other ELB types (Application Load Balancer, Network Load Balancer).
Actions
-
Resolve errors with associated backends
-
Assess the need for the Load balancer
-
Evaluate the existing network architecture
Amazon RDS Idle DB Instances
Description
-
Checks the configuration of your Amazon Relational Database Service (Amazon RDS) for any database (DB) instances that appear to be idle.
-
If a DB instance has not had a connection for a prolonged period of time, you can delete the instance to reduce costs. A DB instance is considered idle if the instance hasn't had a connection in the past 7 days. If persistent storage is needed for data on the instance, you can use lower-cost options such as taking and retaining a DB snapshot. Manually created DB snapshots are retained until you delete them.
Actions
-
Delete the RDS Instance if not needed
-
Troubleshoot the lack of network traffic
-
Reduce the RDS Instance size
-
Turn off the RDS Instance when not needed
Underutilized Amazon Redshift Clusters
Description
-
Checks your Amazon Redshift configuration for clusters that appear to be underutilized.
-
If an Amazon Redshift cluster has not had a connection for a prolonged period of time, or is using a low amount of CPU, you can use lower-cost options such as downsizing the cluster, or shutting down the cluster and taking a final snapshot. Final snapshots are retained even after you delete your cluster.
Actions
-
Delete the cluster if not needed
-
Troubleshoot the lack of network traffic
-
Reduce the cluster size