Cloud View - Data#3
Overview
Getting Setup
Using
Recommendations
Overview
Getting Setup
Using
Recommendations
  • Quick Start
  • Getting Started
  • Concepts and Terminology
    • Overview
    • Tag Hierarchy
    • Shared Data
    • Custom Data
    • Actions
    • System Tags
  • Getting data into Cloud View - Data#3

    • Overview
    • Microsoft Azure
      • Azure App Registration
      • Cost Management Exports
      • Enhanced Azure Access
      • Troubleshooting
    • Amazon Web Services
    • Google Cloud
    • Oracle Cloud
    • Alibaba Cloud
    • Tag Mapping
    • Custom Usage
    • Settings
  • Using Cloud View - Data#3
    • Costs and Usage
    • Emissions and Energy
    • Tracking
    • Budgets
    • Reporting
    • Governance & Compliance
      • Overview
      • Watchdog
    • Customer Management
  • Recommendations
    • Azure
    • Amazon
  • Kubernetes Cost Insights
  • Platform Integration and Security

    • API Overview
    • Platform Security & Data Protection
    • Access Management

AWS Compute Optimizer recommendations

For over-provisioned EC2 instances, CloudCtrl pulls detailed findings directly from AWS Compute Optimizer — Amazon's service for analysing resource utilisation and recommending right-sizing changes.

For each Compute Optimizer finding, CloudCtrl surfaces:

  • Why the instance was flagged — for example, CPU over-provisioned or memory under-provisioned.
  • Current and recommended instance type — so you can see exactly what change is being suggested.
  • Estimated monthly saving — based on AWS On-Demand pricing. Note this figure excludes any existing Reserved Instances or Savings Plans you may have, so your actual saving could differ.
  • Performance risk — how likely the change is to affect your workload's performance.
  • Implementation effort — sourced from Compute Optimizer's own effort rating where available.
  • Steps to make the change — a simple guide: verify the workload, stop the instance, change the type, start it again, and validate.
  • A direct link to the instance in the EC2 console.

AWS Compute Optimizer must be enabled on your AWS account to receive these recommendations. Visit the AWS Compute Optimizer getting started page to opt in.


Idle EC2 Instance

An idle EC2 instance has had consistently low CPU usage for the last 30 days, and may be scaled down or sometimes deleted to reduce costs.

To be "Idle" an EC2 instance

  • Has had less than 15% average CPU usage each hour for the last 30 days

Over provisioned EC2 Instances

An over provisioned EC2 instance is under utilised and could be downsized to a smaller instance type.

This recommendation depends on the Amazon Compute Optimizer, https://aws.amazon.com/compute-optimizer/, which must be opted-in on your account.

  • Visit the getting started page from Amazon, https://aws.amazon.com/compute-optimizer/getting-started/, to enable compute optimizer.
Prev
Azure