Cut the cloud bill

Find what you do not need on AWS, Azure and GCP

Unused disks, orphan snapshots, forgotten IPs, stopped machines still paying for their disk or idle ones left running. 51 rules spot it read-only and, on Business, the agent removes or switches it off with your approval.

Sample findings

Illustrative data
  • EC2 with CPU < 5%

    Free

    EC2 instances with average CPU below 5% over the last 7 days. Candidates for rightsizing or shutdown.

  • Orphaned EBS snapshots

    Free

    Snapshots whose source volume no longer exists. They occupy space and generate cost with no utility.

  • Unassociated Elastic IPs

    Free

    Elastic IPs reserved but not assigned to any resource. AWS charges for each unused IP.

  • Unattached EBS volumes

    Free

    Storage volumes disconnected from any instance. You pay per GB/month without using them.

  • 51

    cost rules

  • 3 clouds

    AWS, Azure and GCP in one panel

  • 18 free

    6 base rules per cloud on the Free plan

  • With your OK

    the agent acts on Business

The problem

Why the cloud bill carries spend you do not need

Leftovers nobody deletes

Disks left without a machine, snapshots of disks that no longer exist, public IPs reserved and unused. They keep billing every month.

Running when nobody uses it

Development and test environments running at night and over the weekend, machines with near-zero CPU, or stopped ones still paying for their disk.

Nobody sees it until the bill

Each cloud has its own console and report. Without one shared view, the forgotten resource only shows up once it has been paid for.

Resources still billing while unused

The solution

How AAA Sentinel solves it

  1. Connect your accounts read-only

    AWS, Azure and GCP with a read-only role. For the agent to apply changes, you grant write permissions separately: its own role on AWS and additional roles on Azure and GCP.

  2. Rules find what is not needed

    On Free, 6 per cloud: low CPU, unattached disks, orphan snapshots, unused IPs, stopped machines with disks and untagged resources. On Pro and Business, all 51: also idle load balancers and NAT, inactive functions and databases, the wrong storage class, oversized machines and paid extended support, among others.

  3. Switch off out of hours

    For low-CPU machines, the agent can schedule start and stop on AWS, Azure and GCP, always with your approval and on Business.

  4. Remove it with your approval

    On Business and as far as each cloud allows, the agent deletes unused disks (snapshotting them first), snapshots, IPs, load balancers, NAT or functions, stops or resizes machines and changes the storage class. Every action with your approval and a grace period set by the action.

At a glance

What it detects on each cloud

The same rule families on AWS, Azure and GCP. Free ones work on the free plan; Pro ones, from Pro.

What it detects on each cloud
ProviderLow CPU · FreeOrphan disks and snapshots · FreeUnused IPs · FreeIdle load balancers and NAT · ProDatabases with no connections · ProPaid extended support · Pro
AWSYesYesYesYesYesYes
AzureYesYesYesYesYesYes
GCPYesYesYesYesYesYes

Only AWS also has the rule for gp2 volumes that could move to gp3. Free shows up to 10 findings.

What each plan includes

Free

  • 1 account and 3 scans a week
  • 6 base rules per cloud
  • Up to 10 findings

Pro

  • All 51 rules
  • Daily automatic scan
  • Every finding

Business

  • Everything in Pro
  • The agent applies changes with your approval
  • Out-of-hours shutdown
See plans

What it does not do

  • It promises no example savings or percentages: you see what is not needed in your account after the first scan.
  • On Free and Pro it applies no changes: it detects and recommends; the agent acts on Business.
  • It does not split Kubernetes cost by namespace.
  • Without approval it can only stop instances or databases when a lease expires, if you have that playbook, and never protected or production resources. Deleting always needs approval.

Frequently asked questions

It depends on your account, and we give no example figures. After the first scan you see every resource that is not needed in your own bill.