Skip to main content

Cloud FinOps Quick Start

Use this guide to start a Cloudaware Cost Management rollout. It focuses on the minimum sequence needed to connect billing data, make spend attributable, and give finance, FinOps, platform, and application teams a shared cost view.

Before You Start​

Confirm that you have:

  • An active Cloudaware account with CMDB enabled.
  • Access to configure cloud and billing integrations.
  • A list of in-scope cloud accounts, subscriptions, projects, tenants, or Kubernetes clusters.
  • Access to billing exports or billing administrator support for each provider.
  • Initial ownership metadata, such as account owners, applications, environments, cost centers, business units, or customers.
  • Agreement on the first cost scopes to report, such as total cloud spend, production applications, shared platforms, or customer-facing services.

Connect Inventory First​

Cost Management depends on CMDB context for ownership, application mapping, and resource metadata. Before onboarding billing data, confirm that the relevant cloud inventory is connected and updating.

Start with:

Enable Billing Sources​

Connect each provider's detailed billing export or billing API so Cloudaware can ingest cost and usage records.

Use the provider guide that matches your environment:

After setup, validate that new billing data arrives on the expected cadence and that the billing period, payer, account, subscription, project, service, and usage dimensions are populated.

Check Cost Management Requirements​

Review the Cost Management prerequisites before expanding reporting to a wider audience.

Use Cost Management Requirements to confirm:

  • Required billing exports and storage destinations are configured.
  • Cloudaware has least-privilege access to billing data.
  • Tagging and allocation prerequisites are defined.
  • Financial data access is controlled with appropriate permissions.
  • FinOps, finance, and platform owners agree on initial operating responsibilities.

Define Allocation​

Start with a small allocation model that can be explained and audited. Prioritize the dimensions needed for the first reporting cycle, then improve coverage over time.

Recommended sequence:

  1. Define required tags and labels with Tagging Strategy.
  2. Map accounts, subscriptions, projects, tags, and CMDB metadata with Business Mapping.
  3. Decide how to split indirect spend with Shared Cost Allocation.

Track unallocated spend separately so owners can see where tagging or mapping needs cleanup.

Publish Initial Views​

Create the first dashboards and reports around questions stakeholders already ask:

  • What did we spend this month?
  • Which providers, services, accounts, applications, or teams drove the change?
  • How much spend is allocated, unallocated, shared, or committed?
  • Which budgets, forecasts, anomalies, or optimization opportunities need attention?

Use:

Add Guardrails​

After baseline reporting is trusted, add controls that help teams act before cost issues become month-end surprises.

Set up:

Start Optimization​

Use optimization workflows after data freshness, allocation, and ownership are reliable enough for teams to trust recommendations.

Begin with:

Review savings opportunities with application and platform owners before making changes that may affect performance, availability, or support commitments.

Next Steps​