Cost Explorer · Accounts · Services · Regions

Your AWS spending.
Find the right levers.

Review AWS spending by account, service and region using Cost Explorer. Follow its evolution, set budgets and qualify available recommendations before deciding on changes to your resources.

  • Costs by account, service and region
  • Read-only AWS access
  • Optional AI
01 — SeeIllustrative product scene · NovaRetail AWS · Fictional November 2026 data
Fictional observed spending
9,880 €
Fictional month-end forecast
19,760 €
Fictional AWS accounts
4

Fictional amounts, with no promise of savings. Cost Explorer and forecasts depend on availability; AWS may charge for API calls. Inventory and advice depend on permissions.

01See

From the AWS total
to the costs behind it.

Cost Explorer provides a view of spending by account, service and region. With a management account and the relevant access, review linked accounts too: distinguish the items that make up the total and identify those to investigate with their owners.

Up to twelve months of history and AWS forecasts where available. Usage costs exclude taxes, credits and refunds; US dollars are converted to euros. AWS may charge for Cost Explorer API reads.

Prepare the AWS connection
Move2Cloud FinOpsThe actual product.

Actual product screenshot — FinOps for AWS

AWS recommendation details for the staging-web-1 instance: finding, potential saving and follow-up in FinOps Move2Cloud, using fictional data.
Actual application screenshot — an AWS recommendation, the affected resource, its potential saving and follow-up. Fictional data, with no promise of savings.Enlarge to explore

3dimensions: account, service and region

12 monthsof history at most, subject to availability

Readcosts; inventory and advice require the relevant permissions

A decision example

From an AWS cost item to a documented decision.

Illustrative workflow using the fictional NovaRetail data above; no customer results or guaranteed savings.

Before
An AWS organisation total alone does not explain which account, service or region caused a variance.
The review
In NovaRetail, filter costs by account, service and region; compare forecasts with the budget and review the flagged anomaly when available.
The next action
Open recommendations available with your permissions. Check usage and dependencies before taking action on EC2, S3 or RDS.

Understand your bill

From total AWS spend to its underlying drivers

Collection uses AWS Cost Explorer. Available dimensions give you a concrete starting point for analysis.

Accounts and services

Review the AWS accounts accessible through your connection, their services and regions. A management account can provide linked account costs according to the permissions granted.

History and forecast

See up to twelve months of history and the month-end forecast supplied by AWS, when those data are available.

An explicit cost basis

AWS usage costs are tracked before taxes, credits and refunds. Dollar amounts are converted to euros using the platform’s reference exchange rate.

Data depend on Cost Explorer and the latest synchronization. AWS may charge for calls to this API.

02Anticipate

An AWS budget.
A deviation to understand.

Set a monthly AWS or tracked-account budget, then configure the threshold and alert recipients. Compare synchronised consumption with that envelope and the available forecast before returning to the services behind a deviation.

The scenario below concerns a fictional AWS account, separate from the opening scene’s provider total. Alerts use the latest collected data; they do not replace AWS billing or provide real-time measurement.

Explore budgets and analysis

Spot spending drift

Give your AWS spend a budget framework

Budgets for your scope

Set a monthly budget for AWS or a tracked AWS account. Choose the threshold that should trigger an alert.

A shared view

Use the overview and dashboards to follow spending trends, then share the view with authorized members of your organization.

Alerts you configure

Set recipients and available channels. Alerts use synchronized data; they are not real-time billing monitoring.

Monthly budget · Fictional example

Fictional AWS account · nova-storefront-prod · November 2026

Observed€4,940
Budget€9,000
Forecast€9,880
Collected spendForecast
Fictional data. Estimates evolve as data is collected and according to each provider’s billing rules.

03Act

An opportunity matters
when you can verify it.

Where inventory permissions allow, review unattached EBS volumes, old snapshots and unused IP addresses. Check usage and dependencies, then organise priority and follow-up before carrying out any changes in AWS.

Cost Optimization Hub advice requires activation and the associated permissions. Metrics do not cover every resource in the same way; savings remain conditional estimates, with no guaranteed bill reduction or automatic infrastructure change.

Understand recommendations

Prioritize actions

Recommendations grounded in accessible data

The opportunities shown depend on permissions, the services you use and the data actually collected.

Recommendations grounded in accessible data
Provider or scopeData and coverage limits
AWS inventoryWith the required permissions, FinOps examines resources such as unattached EBS volumes, old snapshots and unused IP addresses. Review each opportunity against your operational requirements.
AWS adviceCost Optimization Hub recommendations are read when that service is enabled and authorized. Without these conditions, cost collection remains separate from recommendation collection.
Metrics where supportedSome checks use metrics, for example for ECS sizing. Their availability does not imply equal metrics coverage across all AWS resources.

Savings figures are conditional estimates. FinOps does not change your AWS resources or guarantee a lower bill.

From a signal to a tracked action.Illustrative workflow · Subject to plan and permissions
  1. 01 / Review

    A finding.
    Its context.

    Check conditions and available data

    To review
  2. 02 / Decide

    A decision.
    A priority.

    Confirm usage and dependencies

    To qualify
  3. 03 / Track

    A team.
    A tracked action.

    Assign follow-up to an authorised member

    In progress

A plan for your scope

From your first cloud to teamwork.

Start with 14 days on Standard, with no card or IBAN at signup. Then choose according to your scope.

Standard

€69 excl. VAT / month

For a small team’s cost and budget tracking.

  • Up to €5,000 in tracked cloud spend per month
  • 3 connections · 2 members · 5 dashboards
  • 800 AI credits / month, if AI is enabled
  • Budgets, alerts and direct cost allocation

Pro

€249 excl. VAT / month

For tracked actions, measured savings and responsibilities.

  • Up to €20,000 in tracked cloud spend per month
  • 10 connections · 5 members · 20 dashboards
  • 1,500 AI credits / month, if AI is enabled
  • Savings Tracker, Slack, Teams, Jira, GitHub and GitLab

Starter — free, up to €1,000 tracked spend / month and 1 connection. Without a subscription after the trial, the organisation continues on Starter, within its limits.

Enterprise — on quote, for a tailored scope and governance. Discuss your requirements →

Compare all plans →

An explicit framework

The detail, when you need it.

Your next steps

From connection to decision

Create your organization

Open your FinOps workspace, then go to cloud accounts. Configure the AWS connection in the console after signing up.

Authorize reading

Use the proposed AWS role or dedicated credentials. The connection check shows permissions and any limitations before collection.

Review and prioritize

After synchronization, review costs, set budgets and examine the available recommendations before making changes in AWS.

Understand the requested access

AWS within your organization

Your AI choice, with room for other clouds

Optional AI

Your organization chooses its AI policy: AI disabled, Sovereign AI or Standard AI. Cost views and budgets do not require AI to be enabled.

Application hosting in France

French application hosting and the location of AI processing are separate scopes. European-mode requests follow the documented EU and EFTA scope; some provider technical metadata may be handled outside that region.

AWS alongside your other clouds

Add Azure, Google Cloud, OVHcloud Public Cloud, Scaleway or Scalingo to the same workspace. Sources, granularity and credit treatment differ by provider.

Review the data processing scope

Control stays in your hands.

Your data.
Your rules.

Permissions define the view.

Costs, inventory and native advice have different prerequisites. The connection identifies the permissions and limits available.

Your resources stay under your control.

FinOps reads authorised data without resizing or deleting AWS resources. Displayed savings remain estimates to validate.

AI remains optional.

The owner chooses the policy. The application is hosted in France; that does not describe the full scope of AI processing and integrations.

Start by making your AWS spend understandable.

Your AWS account.
Your next clear view.

Explore the platform, then connect accounts from your FinOps workspace and set your team’s priorities.

  1. 01

    Create your workspace.

    Open your organisation, then the AWS connection in the console.

  2. 02

    Authorise reading.

    Configure the proposed role or dedicated credentials and review permissions.

  3. 03

    Review, then prioritise.

    After synchronisation, follow spending and the recommendations actually available.

Before you begin

The right
questions.

Which AWS permissions are required?

Cost collection needs Cost Explorer permissions. Inventory, metrics and recommendations require additional permissions for their respective scopes. The connection flow presents the necessary access; a dedicated role lets you revoke it from AWS.

Can I track several AWS accounts?

Yes. You can connect several accounts. A connection from an AWS organization’s management account can also provide linked account costs, depending on available permissions. Cost visibility and inventory visibility remain separate.

Do the amounts match my AWS invoice?

Tracking uses the usage cost returned by Cost Explorer, before taxes, credits and refunds. Dollar amounts are converted to euros. These conventions, data freshness and the selected period can explain differences from an invoice.

Why might an AWS recommendation be missing?

It depends on the collected data. Cost Optimization Hub must be enabled and authorized for its advice; inventory and metrics checks have their own permission requirements. Missing data do not mean there are no possible optimization actions.

Does FinOps apply optimizations in AWS?

No. FinOps reads data and helps you review actions. Your team decides and makes changes in AWS using its approval procedures. Any estimated saving must be checked against your usage and contracts.

Do I need AI to analyze my spend?

No. Collection, cost views, budgets and rule-based recommendations do not require AI. AI-assisted analyses and compositions follow your organization’s policy, availability and limits.