CoreFinOps Docs
On this page

Quickstart and First Workspace

Follow the shortest path from sign-in to trustworthy first insights.

Before you begin

Have a CoreFinOps workspace, permission to add an AWS connection, a customer AWS account whose owner can deploy a CloudFormation stack, and — when financial spend is needed — a supported AWS CUR 2.0 / Data Export stored in S3. If you are starting with migration planning, prepare a legacy inventory spreadsheet instead.

Quickstart

  1. 1

    Sign in and select a workspace

    Access is scoped to your membership and permissions. New-workspace creation or a trial depends on the enabled commercial release configuration.

  2. 2

    Choose the first source

    Use a synthetic demo workspace for a tour, connect AWS for current inventory, or import legacy estate records for migration work.

  3. 3

    Connect AWS read-only

    Follow Settings → AWS Connections. Deploy the generated customer role with its ExternalId and validate the role through STS.

  4. 4

    Configure billing exports if spend is needed

    Inventory alone does not produce authoritative monthly costs. Configure the billing export and its S3 access separately.

  5. 5

    Run the available jobs

    Inventory, cost ingestion, allocation and recommendation refresh are distinct jobs. Watch their status instead of assuming that saving a connection means all data has arrived.

  6. 6

    Review first value

    Start with Overview, unmapped resources and the Migration Portfolio. Understand the period, currency, measure and freshness before making decisions.

Expected first results

After only an inventory refresh, resource records may appear while monthly spend remains unavailable. After importing application rows, the Migration Portfolio may populate before AWS costs exist. The Value Ledger remains empty until verification evidence is recorded.

Important

Do not use demo figures in a live business case. Synthetic data must be isolated and visually identified as demo data.

If something is empty

A dash means an authoritative value was not returned. Zero applications means no application records are visible to the selected workspace. An empty recommendation list may mean the AWS source is not enrolled, has not refreshed, has no qualifying recommendations, or has insufficient coverage.