Docs / User Guide / Core Setup in 30 Minutes for Cloud Cost Optimization Tools
Product Guide Series - Part 7

Cloud Waste Scanner User Guide Part 7: Core Setup in 30 Minutes for Cloud Cost Optimization Tools

Follow these steps in order: account, proxy, notification, first scan, findings action, and report export.

J By Jerry Reading time: 3 min

Goal

One usable setup session

You should finish with a connected account, one tested route, and one exported result.

Approach

Task-only guide

This page keeps theory out of the way and focuses on what to click and validate.

Result

A repeatable baseline

Once this path is stable, you can repeat it across more accounts without guesswork.

This guide is task-only. No theory, no extra setup paths. Start from Step 0 and stop at Step 7.

Quick Start Steps

  1. Open the guide workflow in Cloud Waste Scanner and keep scope minimal for first validation.
  2. Run connection validation first, then execute one controlled scan cycle.
  3. Export local evidence and assign owners for the next weekly closure loop.

Cloud Waste Scanner runs entirely in your local environment. Your cloud credentials and scan results never leave your machine.

Teams evaluating cloud cost optimization tools usually operationalize this flow with cloud cost optimization for small business and no agent cloud cost optimization. This guide keeps cloud cost optimization tools practical for weekly execution without adding control-plane friction.

If you are evaluating cloud cost optimization tools, this is the fastest way to run a real setup session. It also gives your team a practical baseline when comparing cloud governance tools and FinOps tools.

Most teams do not need more features on day one from cloud cost optimization tools. They need one clean setup path they can finish without second-guessing every screen.

Cloud Waste Scanner dashboard after initial setup.
Target state: dashboard visible, account connected, and first scan ready.

Step 0: Prepare inputs (2 minutes)

  1. One cloud account credential set (read-only preferred for first run).
  2. Proxy endpoint (only if your network requires it).
  3. One notification destination your team already uses.

Step 1: Add and validate your first cloud account (5 minutes)

  1. Open SettingsCloud Accounts.
  2. Click Add Account.
  3. Fill provider, account name, region/profile, and credentials.
  4. Save the account, then click Test Connection inside account details.
Edit Account panel showing credentials and the Test Connection action.
Complete one account end-to-end first, including the connection test.

Step 2: Configure proxy policy when required (3 minutes)

  1. Open SettingsProxies.
  2. Set default proxy mode, or add a named proxy profile.
  3. Run Test Proxy and continue only after it passes.
Proxy policies page with default mode and named proxy profiles.
Lock proxy settings before the first production scan in restricted networks.

Step 3: Create one notification channel and send a test (3 minutes)

  1. Open SettingsNotifications.
  2. Create one channel your team already uses.
  3. Click Send Test Notification, then save after successful test.
Notification channel form with trigger policy and test notification result.
Keep one working channel first; add more channels after the baseline setup is done.

Step 4: Confirm account list and run first scan (5-10 minutes)

  1. Open scan wizard and select 1-2 accounts for the first run.
  2. Start scan from the main screen.
  3. Wait for the Scan Result page and verify findings are populated.
Scan wizard target step with account selection before launching scan.
Keep scope small on the first run so results arrive quickly and are easy to review.

Step 5: Handle findings with two actions (5 minutes)

  1. Select high-impact findings first.
  2. Use Generate Plan for items that should move into review or controlled execution.
  3. Use Ignore for items already processed outside the app or intentionally left out of scope.

Keep the first session simple. The point is to prove that findings can move from discovery into a team workflow without confusing extra states.

Step 6: Export evidence (2 minutes)

  1. Export PDF for management review.
  2. Export CSV for engineering follow-up.
  3. Store both files with scan date in the filename.

If the report will be discussed in a meeting, enable checklist columns in the PDF export so owners can record decisions in the same document.

Export workflow for report output after scan.
Export right after the first scan while context is still fresh.

Step 7: Final check (1 minute)

  • At least one account tested successfully.
  • Proxy applied and re-verified (if required).
  • First scan completed with findings shown.
  • At least three findings reviewed, ignored, or moved into plan generation.
  • PDF or CSV exported.
Final checklist concept image to close the setup flow.
Use this final checklist before rolling the same setup to more accounts.

Next in the series

Part 8 focuses on multi-account naming, routing, and scan-result handling so larger environments stay organized.

Browse all posts: Cloud Waste Scanner Blog. Read this series: Product Guide Series.

Troubleshooting and API Errors

If setup or scan validation fails, use a fixed triage order so your team can resolve issues without guessing.

FinOps Execution Insight

  • Treat each scan as an operating loop: validate inputs, run once, export evidence, and assign owners.
  • Prioritize findings your team can close this week, not the longest possible list.
  • Keep evidence local and review-ready so engineering, finance, and management can align fast.

When to Use CWS vs. Other Approaches

Use Cloud Waste Scanner when you need local-first credential control, deep waste visibility across storage/network/database, and exportable operator evidence. Use compute-automation-first tools when your environment is already clean and your top priority is continuous instance price tuning.

For a complementary perspective, see Spot.io vs Local-First CWS.

Declarative Conclusions

  • CWS is a local-first scanner, meaning credentials and scan outputs remain on your machine by default.
  • Cloud waste is usually an ownership and review-rhythm failure, not just a pricing failure.
  • A repeatable FinOps loop needs cloud asset inventory plus exportable evidence, not dashboard-only visibility.
Try Cloud Waste Scanner

Run Your First 30-Minute Setup

Save your first $1,000 before the next billing cycle.