| Overview | Discover key features of FinOps for Cloud. | /pages/xkcISUCQaUNF0CyOToGV |
| Access Your Organization | Get started by signing in to your organization. | /pages/nUyuUbsJB1vVqu8EHyad |
| Navigate the User Interface | Become familiar with the user interface. | /pages/e90l13kJej3GWnLmHPmK |
| Add Data Sources | Add your AWS, Azure, or Google data sources. | /pages/5rE6SLlLwQOM1zLDuDTe |
| Cost Explorer | Analyze costs and understand the cost structure for your organization. | /pages/UinfEGPN5YuJQJxLrCno |
| Cost Map | View a breakdown of expenses and network transfer costs by location. | /pages/gY5bLMlT9Mv5Y9iLmDom |
| Recommendations | View savings and security recommendations to reduce costs. | /pages/xhEE8TN88X1QLPbwXE73 |
| Resources | Monitor and manage your cloud resources effectively. | /pages/7ap56WSLUwyzpXEakSoz |
| Pools | Group your cloud resources to maximize efficiency. | /pages/jagQG83AtKPSfTzX4UsP |
| Anomaly Detection | Review anomalies and create detection policies. | /pages/GsBPJOOr3vZx7oTO2vYP |
| Quotas and Budgets | Create quotas and budgets and set up alerts. | /pages/EPbw3HZ2f6nfIvyu6kbr |
| Tagging Policies | Create and manage tagging policies. | /pages/0ZsJlwzpNv2Mv6jHco64 |
| User Management | Add or remove members from your organization. | /pages/GtKoLony7cdefWqsdv63 |
| Settings | Manage your invitations and notification settings. | /pages/flDkNaRn9JQ2isSH99KY |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Data Sources | Cloud Tenant Setup |
| Amazon Web Services | ||
| Google Cloud Platform | ||
| Microsoft 365 | ||
| Microsoft Azure |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Pools | Custom Groups |
| Resource allocation | Allocate resources by name, ID, tags, data source, resource type, and region. | Allocate resources by tags or virtual tags. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Pools + Resources | Dashboard + Reports |
| Customizable dashboards | Configuration of tiles to represent data. | |
| Cost drill-down | Ability to filter data using categories (such as service, region, resource type, data source, owner, pool, and more) and periods (daily, weekly, or monthly). See Resources. | Ability to filter data using categories (such as platform type, provider, tenant, subscription, custom group, provider, resource name, tag, and more) and periods (half-year, monthly). See Reports. |
| Detailed reports | Reports can be customized to focus on specific metrics or time periods. They can also be downloaded, emailed, or published to SFTP. | |
| Consolidated consumption | Costs are displayed on a chart (bar or linear) with details placed in a table. See Resources. | Different chart types (such as bar, linear, area, horizontal bar, and pie) and tables (table, summary table) are used to display costs. See Reports. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Recommendations | Recommendations + Cloud Cost Optimization |
| High level overview | Main data overview contains information like total possible monthly savings, check time log, savings with commitments and savings on storage. | Overview of savings breakdown by Strategy, Total Predicted Cost, and Total Predicted Savings for 1 or 3 years. |
| Recommendations filtering | Based on categories (such as Savings, Security, or Critical) and applicable cloud provider services. | Based on categories (such as Cost Optimization, Operational Excellence, or Security) and applicable cloud provider services. |
| Recommendation options | Information with short description, assigned category, affected cloud providers, affected resources, potential savings (in total and per each resource), actions (download report, settings, exclude pools, pin) and settings (each recommendation has its own conditions that can be updated during every auto check). | Shows Cost Optimization Strategy with predicted savings in the chosen currency or as percentage. Also includes a description of the purpose of chosen change. |
| Legacy data | Access to Archived recommendations. | Access to Realised and Unrealised recommendations. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Tagging Policies | Tags |
| New tags setup | Tagging policy must specify if tag is required, prohibited, or if there's a correlation. Resources affected by the policy are chosen based on filters, such as suggested filters, data source, pool, region, service, resource type, resource state, with recommendations, with violated constraints, paid network traffic from/to. | Allows you to manage and create tags. You can also specify the rule, name, add a new tag, or group as a new tag. You can also select an existing tag or create a new tag if it doesn't exist. Additionally, you can filter resources based on criteria, such as resource type, region, service, and more. Additional options include 'With recommendations', 'With violated constraints', and 'Paid network traffic from/to'. Resources are displayed in a table containing columns, such as Resource Name, Data Source, Pool, Region, Service Name, Resource Type, Resource State, and Software Asset. |
| Virtual tags | | |
| Uploading tags to cloud provider | Manage tags in manual or automated Resource rules based on resource properties, option to write tags back to vendor. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Quotas and Budgets | Budgets |
| Cloud budget manager | Tabular view when creating a new quota or budget policy is possible. Each policy allows you to review resources grouped by configured filters. | Configurable views to display Consumption and Utilization grouped by Custom Groups or Provider. |
| New budget setup | Budget policy must contain the type, such as resource quota, recurring budget, or expiring budget. Resources affected by the policy are chosen based on filters, such as suggested filters, data source, pool, region, service, resource type, resource state, with recommendations, with violated constraints, tags, and paid network traffic from/to. | Allows you to set up a budget by specifying the parent group name, name, total amount in USD, start date, end date, and owner email address. Resources affected by the budget are chosen based on filters such as suggested filters, data source, pool, region, service, resource type, resource state, with recommendations, with violated constraints, tags, paid network traffic from/to. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Chargebacks | Chargebacks |
| Chargebacks | Allows you to distribute cloud spend to the relevant business units and cost centers across your organization. You can select the account for which you want to add chargebacks by specifying details such as date, amount, and reason, and add multiple chargebacks. The form includes a table listing of your existing chargebacks. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Anomaly Detection | Alerts |
| New anomaly detection setup | The anomaly detection policy must specify the type, such as Resource Count or Expenses. Resources affected by the policy are chosen based on filters such as suggested filters, data source, pool, region, service, resource type, resource state, with recommendations, with violated constraints, tags, paid network traffic from/to. | Three types of cloud consumption alerts are supported, including Spike Alerts, Overage Alerts, or Reserved Instance Utilization. Spike alerting identifies usage anomalies in Azure or AWS environments. Overage alerting notifies you if consumption exceeds defined values. Reserved Instance alerting monitors the utilization of reservation purchases. |
| Manage anomaly detection | List of all implemented policies with their names, visualization of the status, short description and applied filters. | List of implemented alerts with their names, type, visibility, last run, along with the most important columns to quickly grasp the context of the definition. |
| Anomaly detection details | Detailed information about the policy together with detailed history showing all historical violations. | The preview section is a graphical representation of the alert, highlighting the time at which it occurs. You can interact with this chart, which includes 'hover-over text' when viewing a vertical bar in the chart. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Events | N/A |
| List of historical events | General list of events with simple filtering by All, Info, Warning, Error. You can also check event details, such as exact date, object name, object type, and short description. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | User Management | N/A |
| Roles and permissions | Supports four types of permissions, including Organization Manager, Manager, Engineer, and Member. | User management (Moved to Marketplace in v2) |
| Name | Organization | Collaboration Site |
| Multi-organization approach | A user can be a part of different organizations and can switch between them using the Organization menu. | A user can be a part of different organizations with different role and can switch between them. |
| Document collaboration | Store and share large files conveniently. |
| Feature | FinOps for Cloud | Cloud Spend Management |
|---|---|---|
| Name | Settings | Alerting |
| Reporting | ||
| Alerts | ||
| Notification settings | The Organization Manager can change notification settings. Notifications can be enabled or disabled from these modules: FinOps, Policy Alerts, Recommendations, System notifications, and Account management. | Supports individual notifications with an option to share the notifications with other users. |
| Notification service | Portal only, email and/or SMS |
| What do you want to do? | See this page for details |
|---|---|
| Set quotas and budgets to manage your cloud spending effectively. | Quotas and Budgets |
| Allocate resources by name, ID, tags, data source, resource type, and region. | Pools |
| Create tagging polices to categorize your resources. | Tagging Policies |
| Identify anomalies in your spending. | Anomaly Detection |
| View savings and security recommendations. | Recommendations |
The password recovery email.
The email verification code.
The registration page for FinOps for Cloud.
Accept your pending invitation.
The Home page in SoftwareOne FinOps for Cloud.
The Data Sources page in FinOps for Cloud.
The Cost Explorer in FinOps for Cloud.
The Region cost map in FinOps for Cloud.
The Network traffic cost map in FinOps for Cloud.
Recommendations in FinOps for Cloud.
on the card and selecting **Settings**.
{% endhint %}
### Abandoned instances
Instances that have an average CPU consumption of less than **5%** and network traffic below **1000 bytes/s** for the last **7 days**. We recommend terminating these instances to reduce expenses.
### Obsolete images
Images that haven't been used for a while might be subject to deletion, which would unlock the underlying snapshots. Image selection criteria:
* The image creation date was more than 1 week ago.
* No instances have been created from/related to this image in the past **7 days**.
You can download the list of obsolete images as JSON for subsequent automated processing with the help of [Cleanup Scripts](/insights/recommendations/clean-up-scripts-based-on-recommendations).
### Obsolete snapshots
Redundant and old snapshots save up on storage expenses if deleted. You can download the list of snapshots as JSON for use in further implementations like clean-up scripts and maintenance procedures. Selection criteria:
* The source EBS volume doesn't exist anymore.
* No AMIs are created from this EBS snapshot.
* It hasn't been used for volume creation for the last **4 days**.
The list of obsolete snapshots can be downloaded as JSON for subsequent automated processing with the help of [Cleanup Scripts](/insights/recommendations/clean-up-scripts-based-on-recommendations).
### Obsolete IPs
Obsolete IPs can be tracked for Azure and AWS clouds to reduce expenses. The following is the selection criteria for the obsolete IPs:
* The IP was created more than **7 days** ago.
* The IP hasn't been used in the last **7 days**.
* It costs money to be kept.
### Not attached volumes
Notification about volumes that haven't been attached for more than one day. These are considered to be forgotten or no longer relevant. We recommend that you delete such resources.
You can download the list of unattached volumes as JSON for subsequent automated processing with the help of [Cleanup Scripts](/insights/recommendations/clean-up-scripts-based-on-recommendations).
### Underutilized instances
This recommendation is aimed at the detection of underutilized instances in AWS and Azure and suggests more suitable flavors for these machines. An instance is considered to be underutilized if:
* It is active.
* It has existed for more than **3 days**.
* Its CPU metric average for the past **3 days** is less than 80%.
### Reserved instances opportunities
This card contains instances that are active and have sustainable compute consumers for more than **90 days**. Instances that haven't been covered with Reserved Instances or Saving Plans are also included.
For all such instances, consider purchasing Reserved Instances to save on compute usage. Check **RI/SP Coverage** to see the detailed breakdown of current reservations.
### Abandoned kinesis streams
This card shows Kinesis Streams with provisioned Shard capacity that haven't performed operations in the last **7 days**. Consider removing them to reduce expenses.
### Instances with migration opportunities
This card shows opportunities to migrate instances if the tool detects that the same instance type is cheaper in a geographically close region (within the same continent).
Some of your active instances might cost less in another nearby region with the same specifications. Consider migrating them to the recommended region to reduce expenses.
### Instances for shutdown
This recommendation means that some of your instances have an inactivity pattern that allows you to set up an on/off power schedule (average CPU consumption is less than **5%** and network traffic below **1000 bytes/s** for the last **14 days**). Consider creating a power schedule to reduce expenses.
### Instances with spot (pre-emptible) opportunities
This list contains instances that:
* Are running for the last **3 days**.
* Have existed for less than **6 hours**.
* Were not created as Spot (or Preemptible) Instances. Consider using Spot (Preemptible) Instances.
### Underutilized RDS instances
An underutilized instance is one average CPU consumption of less than **80%** for the last **3 days**. FinOps for Cloud detects such active RDS instances and lists them on the card. Consider switching to the recommended size from the same family to reduce expenses.
### Obsolete snapshot chains
Some snapshot chains don't have source volumes or images created from their snapshots and have not been used for volume creation for the last **3 days**. Consider their deletion to save on snapshot storage expenses.
### Instances with subscription opportunities
The instances in the list are active and have been identified as sustained compute consumers (for more than **90 days**) but are not covered by subscription or Savings Plans. Consider purchasing subscriptions to reduce computing costs.
### Not deallocated instances
Detection of inactive, non-deallocated machines that have not been running for more than **1 day** and are still billed by the cloud.
You can download the list of non-deallocated VMs as JSON for subsequent automated processing with the help of [Cleanup Scripts](/insights/recommendations/clean-up-scripts-based-on-recommendations).
### Instances eligible for generation upgrade
Upgrade older generation instances to the latest generation within the same family.
### Abandoned Amazon S3 buckets
A bucket is abandoned if the average data size is less than **1024 megabytes**, the Tier1 request quantity is less than **100**, and the `GET` request quantity is less than **2000** for the last **7 days**.
We recommend that you delete it to reduce expenses. Change the check period and other parameters in the card's **Settings**.
# Security Recommendations
### Inactive IAM users
Users who have been inactive for more than **90 days** are considered obsolete and subject to deletion. This is due to the security risks they pose for the organization, as they can be compromised and become access points for malicious users.
The number of days is a custom parameter. Use **Settings** to change it. You can also download a list of inactive users as JSON or XLSX by selecting the download icon Inactive IAM users
The Archive option on the Recommendations page.
in a recommendation card contains features that you can use to adjust parameters and exclude pools.
These features allow you to fine-tune and optimize results to better meet specific goals or conditions. The available parameters and pools you can exclude from a recommendation vary based on the recommendation you are accessing.
## Customizing a recommendation
To customize a recommendation:
1. Navigate to the **Recommendations** page.
2. Find the required recommendation, then select the more icon.
3. To update the recommendation parameters, select **Settings** and make the required changes. When saved, new settings are applied during the next recommendations check.
4. To exclude a pool from a specific recommendation, select **Exclude pools**. When excluded, the excluded objects are displayed on the **Excluded** tab within the **Recommendations** page.
5. To pin or unpin a recommendation, select **Pin** or **unpin**, depending on the available option. Pinned recommendations always appear as the first one in your list of recommendations until they are unpinned.
{% hint style="info" %}
The option to pin a recommendation is only available in the card view.
{% endhint %}
# Clean-up Scripts Based on Recommendations
{% hint style="danger" %}
The script deletes all recommended resources (based on the downloadable JSON file) and ignores errors. After completion, a summary lists deleted resources, non-existent or already deleted resources, and resources that couldn't be deleted due to other reasons.
{% endhint %}
## Amazon Web Services (AWS)
### Prerequisites
* [AWS Command Line Interface (AWS CLI)](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
* jq - The package allows executing JSON scripts with bash. See [Download jq](https://stedolan.github.io/jq/download/).
### Implementation
1. Install the requirements on a machine running Linux OS.
2. Configure the AWS Command Line Interface. (Run the **aws configure** command. For information, see the [AWS User Guide](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html)).
3. Download the script from the corresponding subsection on the **Recommendations** page.
4. From the same page, download the JSON file containing a list of all resources recommended for deletion.
5. Run the script as follows: `bash The Resources page in FinOps for Cloud.
The Actions column containing an option to delete a perspective.
The Constraints tab on the resource details page.
Available constraint type
| Type | Key/Value | Description |
|---|---|---|
| Name/ID starts with | string value | Matches resources where the name or ID begins with the specified value. |
| Name/ID ends with | string value | Matches resources where the name or ID ends with the specified value. |
| Name/ID is | string value | Matches resources with an exact name or ID match. |
| Name/ID contains | string value | Matches resources where the name or ID contains the specified substring. |
| Tag is | key-value pair | Matches resources with a tag that matches both the specified key and value. |
| Tag exists | key-value pair | Matches resources that have a tag with the specified key. |
| Tag value starts with | key-value pair | Matches resources with a tag value starting with the specified value for the given key. |
| Source is | selected row | Matches resources from a selected data source. Options are presented in a dropdown for selecting the source. |
| Resource type is | string value | Matches resources where the resource type contains the specified value. |
| Region is | string value | Matches resources where the region contains the specified value. |
The Assignment rules page displaying all rules.
. You can edit the name of the rule, conditions, and assignment details. You can also enable or disable the rule.
* To set the rule priority to the highest, select 
. The priority of the other rules is then decreased by one.
* To decrease rule priority by 1, select 
. The rule is then swapped with the rule behind it.
* To increase the rule priority by 1, select
. The rule is swapped with the previous rule.
* To assign the rule with the lowest priority across the given organization, select 
. All other affected rules are then updated.
* To delete a rule, select 
. To learn more, see [Delete Pools](/insights/pools/delete-a-pool).
# Reapply Ruleset
The **Re-apply ruleset** option initiates a new check of the already assigned resources against the current ruleset.
When selected, this option reorganizes the resources, even if they were previously assigned otherwise. This feature helps you manage assignments, especially when the rules are edited, new ones are added, or the priority of existing rules is changed.
{% hint style="info" %}
The option to reapply a ruleset is only available to individuals with Organization Manager or Root Pool Manager permissions.
{% endhint %}
## Reapplying a ruleset
To reapply a ruleset:
1. Navigate to the **Pools** page.
2. Select **Configure assignment rules**, then select **Re-apply ruleset**.
3. Choose whether to reapply the ruleset to the resources in the **entire organization** or a **specific pool**.
4. If you selected **Specific pool**, choose the pool from the list. Optionally, select **With sub-pools** to include sub-pools.
5. Select **Run** to start the process.
# Create Pool Constraint Policies
If you want to implement policies for an entire pool, instead of a single resource, you can do so from the **Constraints** option within the pool's details page.
Only individuals with a **Manager** role can enforce shared constraints across the pool. While shared constraints apply pool-wide, custom resource-specific constraints can still be configured and will override the general policy.
## Creating a pool constraint policy
To configure pool constraint policies:
1. Navigate to the **Pools** page.
2. Select the desired pool group or subpool.
3. Go to the **Constrains** tab and select the edit icon.
4. Enter values in the **TTL** (Time-to-live) or **Daily expense limit** fields.
5. Select Pool constraint policies.
Assignment rules for a pool.
.
3. In the confirmation dialog, select **I understand and want to delete this pool**.
4. Select **Delete** to confirm.
When the pool is deleted, all resources from that pool are reassigned to its parent pool. Any rules that previously referenced the deleted pool are automatically redirected to the root pool.
# Anomaly Detection
Anomaly detection is an integral part of a cloud security and management strategy.
It helps maintain the integrity and performance of cloud services while identifying and addressing potential issues before they cause significant damage or disruption. An anomaly is defined as a deviation from the normal pattern of cost or usage for a specific resource or group of resources.
### Anomaly detection in FinOps for Cloud
Anomaly detection in FinOps for Cloud helps you identify unusual behavior that may indicate a security breach, system malfunction, or other operational challenges.
You can create new anomaly detection policies and manage them from the **Anomaly detection** page.
FinOps for Cloud supports two types of anomaly detection policies, including resource count and cost:
* **Resource count** - These anomalies refer to inconsistencies or unexpected variances in the number of resources being utilized or allocated compared to what is expected or provisioned. Resource count anomalies can occur in various cloud resources, such as virtual machines, storage, network bandwidth, or cloud services, like databases and application servers.
* **Expense** - These anomalies refer to instances where the actual financial expenditure on cloud resources deviates significantly from expected or budgeted costs. Expense anomalies can represent underlying issues, such as inefficient resource utilization, misconfigurations, unauthorized access, or even billing errors from cloud service providers.
When creating policies, you can also define the evaluation period, thresholds, and filters.
Anomaly detection in FinOps for Cloud.
The Create anomaly detection policy page in FinOps for Cloud.
The details page of an anomaly detection policy.
.
4. Under **Name**, enter the new name, then save your changes.
### Deleting a policy
{% hint style="warning" %}
Deleted policies cannot be restored.
{% endhint %}
To delete an existing anomaly detection policy:
1. Navigate to the **Anomaly detection** page.
2. In the list of policies, select the policy you want to delete.
3. On the policy details page, select **Delete**.
4. In the confirmation panel, select **Delete** to confirm the action.
# Export Chart
The **Export chart** option on the policy details page allows you to download the chart as a PNG file.
By default, the chart displays data categorized by service along with daily expenses. You can modify these settings using the **Categorize by** and **Expenses** options. Additionally, you can hover over the chart to view detailed information.
The Export chart option to download the chart as a PNG file.
Quotas and budgets in FinOps for Cloud.
Create quota or budget policy in FinOps for Cloud.
.
4. Under **Name**, enter the new name, then save your changes.
### Deleting a quota or budget
{% hint style="warning" %}
Deleted policies cannot be restored.
{% endhint %}
To delete an existing quota or budget policy:
1. Navigate to the **Quotas and budgets** page.
2. In the list of policies, find the policy you want to manage, then select the policy name.
3. On the policy details page, select **Delete**.
4. In the confirmation panel, select **Delete** to confirm the action.
# View Policy Violation History
A violation history is available for those policies where the resource count or the expenses have exceeded the quota or budget.
Violated policies are displayed in red on the **Quotas and budgets** page.
### Viewing the policy violation history
To view the policy violation history:
1. Navigate to the **Quotas and budgets** page.
2. In the list of policies, find the policy for which you want to view the violation history.
3. Select the policy name.
4. On the policy details page, use the **Policy Violations History** section to view details including:
1. The date and time when the policy violation occurred.
2. The budgeted expense value vs the actual expense.
3. The resources linked to the quota or budget.
# Tagging Policies
Tagging Policies are a type of policy that can help ensure that your resources are properly categorized and monitored.
Tagging policies use custom tags, which are descriptive labels assigned to resources. These tags help identify resources among others, making it easier for you to locate and manage them.
### Tagging policies in FinOps for Cloud
In FinOps for Cloud, Organization Managers can create new tagging policies using the **Add** option on the **Tagging policies** page.
When creating a new policy, you can specify the tagging rules applicable to resources when they are tagged. If the policy is violated, FinOps for Cloud sends an email notification to the Organization Manager.
Tagging policies in FinOps for Cloud.
Create a new tagging policy.
The details page of a tagging policy.
. Then, provide the new name and save your changes.
* To delete the policy, select **Delete** and then select **Delete** again in the confirmation panel to confirm the action.
# User Management
The **User management** page in FinOps for Cloud displays a list of existing members within your organization. For each member, you can view details, such as their name, unique ID, last login time, email address, and assigned roles.
From this page, Organization Managers can also invite new members or remove existing members from the organization.
## Role overview
In FinOps for Cloud, roles can be assigned when [inviting a user to the organization](/finops-for-cloud/getting-started/invite-users-to-your-organization).
By default, the Member role is assigned to allow the individual to have read-only access. You can select other roles and assign them at the pool level. When assigning roles, we recommend assigning the Organization Manager role only to those individuals who need the highest level of access and permission to perform actions without any restrictions.
The following table lists the roles in FinOps for Cloud. These roles cannot be edited, and you cannot create new ones.
| Role | Description |
|---|---|
| Member | The Member role is assigned by default to all users. Members have read-only access across the platform and can view dashboards, resources, pools, policies, recommendations, and analysis features. They can also download reports and exports where supported. Members cannot make any modifications to the platform. |
| Engineer | The Engineer role is assigned at the resource level. Engineers can view the entire platform. This includes pool structures, recommendations, and analysis views, but their editing capabilities are limited to the specific resources they are responsible for. All other areas are available in read-only mode. |
| Manager | The Manager role is assigned at the pool level. Managers can administer the pools they have been assigned to, including creating and deleting sub-pools, configuring assignment rules, and re-applying resource assignment rules. This permission cascades downward: a Manager assigned to a pool automatically has the same management permissions over all child pools beneath it, at every level of nesting. Areas of the platform outside their assigned pools are available in read-only mode. |
| Organization Manager | The Organization Manager has full administrative control over the entire FinOps for Cloud environment. This role can invite and remove users, manage all pools and sub-pools across the organization, configure all policy types (anomaly detection, quotas and budgets, and tagging policies), and fully manage data sources. Organization Managers also have unrestricted access to all analysis, reporting, and configuration features. This role should be assigned only to individuals who require the highest level of access. |
| Platform role | Likely personas | Assign this role to people who... |
|---|---|---|
| Member | Finance, Product, Procurement, Leadership, ITAM, Sustainability | Need visibility into cloud spend and usage to inform decisions, reporting, or governance, but have no need to make changes in the platform. A good default for anyone who needs to stay informed without being given edit access. |
| Engineer | Engineering | Build and operate the cloud infrastructure that generates the costs. They need visibility into recommendations and resource data to act on optimization opportunities, but their changes are scoped to the resources they own. |
| Manager | FinOps Practitioner, Finance, ITFM | Own cost accountability for a specific business unit, team, or project. They manage a defined pool of cloud spend and need to act on it, creating sub-pools, assigning resources, and responding to budget alerts, but don't need organization-wide control. |
| Organization Manager | FinOps Practitioner, Leadership | Lead the FinOps practice, own the platform configuration, and need unrestricted access to manage users, data sources, policies, and all pools across the organization. Typically, one or two people. |
| Feature / Permission | Member | Engineer | Manager | Organization Manager |
|---|---|---|---|---|
| View organization overview |
| Feature / Permission | Member | Engineer | Manager | Organization Manager |
|---|---|---|---|---|
| Overview | ||||
| View recommendations | ||||
| Filter recommendations | ||||
| Change view (cards / table) | ||||
| Search recommendations | ||||
| View recommendations archive | ||||
| Run recommendations check | — | — | — | |
| Download script | ||||
| Download xlsx/json | ||||
| Recommendation | ||||
| View recommendation settings | ||||
| Edit recommendation settings | — | — | — | |
| View excluded pools | ||||
| Edit excluded pools | — | — | — | |
| Pin recommendations | ||||
| Dismiss recommendation | — | — | — |
| Feature / Permission | Member | Engineer | Manager | Organization Manager |
|---|---|---|---|---|
| Overview | ||||
| View resources | ||||
| Filter resources | ||||
| View saved perspective (view) | ||||
| Create saved perspective (view) | — | — | — | |
| Export expenses chart | ||||
| Download xlsx/json | ||||
| Resource | ||||
| View resource details | ||||
| Add assignment rule | — | — | 1 |
| Feature / Permission | Member | Engineer | Manager | Organization Manager |
|---|---|---|---|---|
| Overview | ||||
| View pools | ||||
| Add / edit / delete pool | — | — | 1 | |
| Assignment rules | ||||
| View assignment rules | ||||
| Search assignment rules | ||||
| Add / edit / delete assignment rule | — | — | 1 | |
| Reorder assignment rules | — | — | — | |
| Re-apply assignment rules | — | — | 1 |
| Feature / Permission | Member | Engineer | Manager | Organization Manager |
|---|---|---|---|---|
| Cost Explorer | ||||
| View cost explorer | ||||
| Filter cost explorer | ||||
| Download PDF | ||||
| View expense breakdowns | ||||
| Cost Map | ||||
| View map | ||||
| Filter map |
| Feature / Permission | Member | Engineer | Manager | Organization Manager |
|---|---|---|---|---|
| Anomaly detection | ||||
| View anomaly detections | ||||
| Add / edit / delete anomaly detection | — | — | — | |
| View anomaly detection details | ||||
| View anomaly detection resources | ||||
| Export anomaly detection chart | ||||
| Quotas and Budgets | ||||
| View quota or budget | ||||
| Add / edit / delete quota or budget | — | — | — | |
| View quota or budget resources | ||||
| Tagging policies | ||||
| View tagging policy | ||||
| Add / edit / delete tagging policy | — | — | — | |
| View tagging policy resources |
| Feature / Permission | Member | Engineer | Manager | Organization Manager |
|---|---|---|---|---|
| User management | ||||
| Invite users | — | — | — | |
| Download xlsx/json | ||||
| View last login date and time | — | — | ||
| Delete users | — | — | — | |
| Data sources | ||||
| View data sources | ||||
| Add data source | — | — | — | |
| Rename data source | — | — | — | |
| Update data source credentials | — | — | — | |
| Perform billing re-import 2 | — | — | — | |
| Disconnect data source | — | — | — | |
| Events | ||||
| View events | ||||
| Filter and search events | ||||
| Settings | ||||
| View organization details | ||||
| View and accept invitations | ||||
| Manage email notifications 3 |
| Notification | Member | Engineer | Manager | Organization Manager |
|---|---|---|---|---|
| FinOps | ||||
| Weekly expense report | — | — | ||
| Pool limit exceed alert | — | |||
| Pool limit alert | ||||
| Saving spike | — | — | ||
| Policy alerts | ||||
| Resource constraints report | — | |||
| Resource constraint violation alert | — | |||
| Anomaly detection | — | — | ||
| Expiring budget policy violation | — | — | ||
| Quota policy violation | — | — | ||
| Recurring budget policy violation | — | — | ||
| Tagging policy violation | — | — | ||
| Recommendations | ||||
| New security recommendation detection | — | — | ||
| System notifications | ||||
| Environment changed | — | |||
| Expenses initial processing completed | — | — | ||
| Report import failed | — | — | ||
| Account management | ||||
| Invitation notification |
| Term | Definition and use |
|---|---|
| Management account | A management account is an AWS account you use to create your AWS Organization. The owner of the management account is responsible for paying for all usage, data, and resources used by the accounts in the organization. A management account is also called a root account, master account, billing account, or payer account. In FinOps for Cloud, use this account type when adding an AWS Organization management account. |
| Member account | A member account is an AWS account, other than the management account, that is part of an AWS Organization. The management account is responsible for paying for all member accounts in the organization. A member account is also referred to as a linked account, child account, usage account, or sub-account. In FinOps for Cloud, use this account type when adding an AWS Organization member account, and the management account has already been added to FinOps for Cloud. |
| Standalone account | A standalone account refers to an account that is not part of an AWS Organization. It stands on its own, without being linked to any other accounts for consolidated billing, management, or policy control. A standalone account is also referred to as an individual account, non-organizational account, or unlinked account. In FinOps for Cloud, use this account type when:
|
The recommended Cost and Usage Report settings.
Adding a management account to FinOps for Cloud using an assumed role
Adding a member account to FinOps for Cloud using an assumed role
Migrate to CUR 2.0 and update the credentials.
The option to reimport billing data.
Google Cloud data source
Billing export
Google Cloud data source
Schedule import option.
Events page in FinOps for Cloud.
to choose a custom date range for the events you want to view.
### Searching for an event
To search for a specific event, enter a keyword in the **Search** field and press **Enter**.
### Viewing event details
To view detailed information for an event, select the event.
You can then view the date and time the event occurred, a description of the event, and details of the object involved in the event.
# Settings
The **Settings** page in FinOps for Cloud lets you view and manage your organization settings, account invitations, and email notifications.
Settings page within FinOps for Cloud
| General FAQs | Find answers to the common questions about, FinOps for Cloud, including setup, access, and more. | /pages/n9cz6Kijpp4WKPHizRSY |
| Billing and Invoicing FAQs | Find answers to questions about pricing, invoices, billing cycles, and more. | /pages/UBCOussZkMOyN1b6seEH |
| Data Sources FAQs | Find answers to questions about adding and managing data sources. | /pages/FjYntsj3tfWkUTeHm5jT |
| Component | FinOps for Cloud | SoftwareOne invoice |
|---|---|---|
| Amount | Always shows the estimated amount for the current period. | Always shows the exact amount. |
| Subscriptions | Contains subscriptions from all connected cloud service providers. | Contains SoftwareOne subscriptions only. |
| Data availability | Available daily, even before the invoice has been issued. | Available monthly, only after the invoice is generated. |
| Other features | Offers enhanced features, like tagging policies and budgets. | Doesn't offer advanced analytics and monitoring. |