×

Welcome to Knowledge Base!

KB at your finger tips

This is one stop global knowledge base where you can learn about all the products, solutions and support features.

Categories
All
Storage and Backups-Nutanix
Beam User Guide

Beam Hosted

Last updated: 2022-10-31

Beam Overview

Beam is a Cost Governance SaaS product offering by Nutanix that helps cloud-focused organizations to gain visibility into cloud spend across multiple cloud environments.

The following are a few of the key functionalities that help you with the cost management:

  • Provides you with deep visibility and rich analytics detailing cloud consumption patterns.
  • One-click cost optimization across your cloud environments.
  • Proactively identifies idle and underutilized resources, delivers specific recommendations to resize infrastructure services, and ensure optimal cloud consumption.

Beam provides the following capabilities:

  • Visibility into cloud consumption : Provides businesses with deep visibility into their multi-cloud consumption at an aggregate and granular level. Beam also automatically identifies cost anomalies to ensure cloud operators can immediately identify when spending deviations happen.
  • Optimization of Cloud Consumption : Provides cloud operators with a one-click feature and optimization recommendations to easily right-size cloud resources. Beam uses machine intelligence to continuously suggest optimal purchase plans for reserved instances that drive deep cost savings.
  • Control over Cloud Consumption : Helps you to set policies that continuously maintain high levels of cloud cost efficiency by automating various cost-saving actions. You can also create budgets for various teams or projects, track the spending against allocated budgets, and get alerts when a budget exceeds.

Cost Management for Nutanix On-Prem

Beam application enables you to take control of your cloud spend on the Nutanix on-premises resources. The application supports Nutanix enterprise cloud deployments to extend cost visibility capability into the multi-cloud cost governance portfolio.

Beam provides cost visibility into the on-premises clusters and resources. The costs are modeled to reflect the true cost of owning an on-prem infrastructure including Nutanix hardware, software, facilities, administration, and so on. The holistic cost visibility helps you to understand and control the overall cost associated with the Nutanix private cloud environment.

Nutanix cost management supports the following features.

  • True cost of running on-premises infrastructure with the help of a Total Cost of Ownership (TCO) model.
  • Metering and cost visibility of Nutanix clusters and resources on a daily and monthly granularity.
  • Enable financial governance by creating chargeback reports and budget alerts.

The application obtains the purchase and consumption data from Nutanix sales databases, MyNutanix Portal account, and Pulse .

Note: The historical spend reported in Beam is delayed by at least 24 hours as the cost metering is updated only once in 24 hours.

Multicloud Views

Apart from providing cost visibility and optimization recommendations for individual clouds, the application also provides cost visibility and optimization recommendations for entities with multiple clouds (Nutanix, AWS, Azure, and GCP). You can configure two types of multicloud entities - Financial and Scope.

Financial is a hierarchical structure comprising of Business units and Cost Centers used for Chargeback. Chargeback allows you to group cloud resources across multiple clouds (Nutanix, AWS, Azure, and GCP) within Cost Centers and Business units. By design, a cloud resource cannot be part of different cost centers or business units. For more information, see Chargeback.

Scope is a custom resource group with resources across multiple clouds (Nutanix, AWS, Azure, and GCP). Scopes are useful in providing visibility to logical resource groups like applications, project teams, cross-functional initiatives, and so on. Hence, by design, a cloud resource can be part of multiple Scopes. For more information, see Scopes.

User Interface Layout

This section provides information on the layout and navigation of the Beam console.

The Beam console provides a graphical user interface to manage Beam settings and features.

View Selector

When you log on to the Beam for the first time, the View Selector pop-up appears. The View Selector pop-up allows you to search for an account by typing the account name in the search box or navigate and select a cloud account, business unit or cost center, and custom scope.

The Dashboard is the welcome page that appears after logging and selecting a view in Beam.

Figure. View Selector Click to enlarge

For the subsequent logins, the last visited page for the last selected view (account, business unit or cost center, and scope) appears. You can click View in the top-right corner to open the View Selector pop-up and select a different view.

Table 1. Available Views
View Description
All Clouds Select this view to get total cost visibility for AWS-, Azure-, GCP-, and Nutanix-accounts for which you have access.
Nutanix Allows you to select Nutanix-accounts.
Financial Allows you to select business units or cost centers you created for the chargeback.
Scopes Allows you to select the custom scopes you created.

Beam Console

The Beam Console screens are divided into different sections, as described in the following image and table.

Figure. Beam Console Overview Click to enlarge
Table 2. Beam Console Layout
Menu Description
Hamburger icon Displays a menu of features on the left. When the main menu is displayed, the hamburger icon changes to an X button. Click the X button to hide the menu.
Alerts The Alert option allows you to see system-generated alert notifications. Click the bell icon from the main menu bar to view alerts. Click See More to view the complete list of notification.
User Menu The user drop-down menu has the following options.
  • Profile - Displays your account information, timezone and email preferences, and Product Access (read/write) for Beam.
  • What's New - Displays the recent product updates.
  • Terms of Service
  • Privacy Policy
  • Responsible Disclosure
  • Log out - Click to log out of the Beam console.
Help Menu You can click the question mark icon in the top-right corner of the Console to view the following:
  • Read Documentation - Redirects you to the Beam documentation.
  • Guided Tours - Opens the list of walkthrough videos that helps you to navigate through various tasks and workflows in Beam.
Widgets Section The widgets section displays the informational and actionable widgets corresponding to the feature that you have selected from the main menu. For instance, the Dashboard page display widgets like Spend Overview , Spend Analysis , Spend Overview - TCO Cost Heads , and Spend Overview - Virtual Machines .
View option Click View in the top-right corner to open the View Selector pop-up.

Main Menu

Clicking the Hamburger icon displays a menu of features on the left. When the main menu is displayed, the Hamburger icon changes to an X button. Click the X button to hide the menu.

Figure. Main Menu Click to enlarge

The following table describes each feature in the main menu.

Table 3. Main Menu - Available Features
Feature Description
Dashboard Displays the Dashboard page (see Dashboard (Nutanix)).
Analyze Displays the Analyze page (see Cost Analysis (Nutanix)).

Analyze allows you to track cost consumption across all your cloud resources at both the aggregate and granular level. You can drill down cost further based on your services, accounts, or application workload.

Chargeback Displays the Chargeback page (see Chargeback).

Enables the financial control of your cloud spends by providing the ability to allocate cloud resources to departments based on definitions. It provides a consolidated view across all your cloud accounts in a single pane for Finance views.

Budget Displays the Budget page (see Budget).

A budget allows you to centralize the budget at the business unit, cost center, or scope levels to ensure that your consumption is within the budget that you have defined.

Reports Displays the Reports page (see Cost Reports).

Beam generates reports to track cost consumption across all your cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications. The reports are generated automatically and are available to view, download, or share from the Beam console.

Configure menu The Configure menu allows you to do the following operations.
  • Add and manage Nutanix accounts in Beam. For more information, see Onboarding Nutanix Account.
  • Manage Beam users
  • Chargeback
  • Scopes
  • Nutanix Cost Configuration

Administration and User Management

Beam allows you to do the following administrative controls.

  • Add and manage users accessibility to various cloud accounts in Beam.
  • Two types of access can be granted to a user.
    • Admin Access - The user gets read and write access to all cloud accounts added in your Beam account.
    • User Access - The administrator can grant Read Only or Read & Write permissions on selected cloud accounts to a user, thus allowing the administrator to exercise the principle of least privilege.

Adding a Beam User

You can add and manage users using the Beam console.

About this task

To add a user in Beam, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > User Management . Click Add User .
  2. In the Details page, enter the user details and change the timezone as desired. Then, click Next to go to the Permissions page.
    In the Permissions page, you can choose Admin Access or User Access .
  3. Click Admin Access if you want to give administrator rights to the user. See User Roles for details on types of users. Then, click Save to complete the task.
  4. Click User Access if you want to grant Read Only or Read & Write permissions on selected cloud accounts to the user.
    1. Select the required access ( No Access , Read Only , and Read & Write ) across clouds.
      The No Access option is selected by default.
    2. Select the AWS Payer Account and Linked Accounts, Azure Billing Accounts and Subscriptions, Nutanix accounts, and GCP Billing Accounts and Projects for which you want to provide access. Then, click Save to complete the task.
    Figure. User Management - Granting Permissions Click to enlarge

User Roles

This section helps you to understand all the different roles in Beam and when you would use each.

Figure. Beam User Roles Click to enlarge User Roles
Owner Role

When a user creates a Beam Subscription , a tenant is triggered and the user becomes the owner of that tenant.
 An owner is shown as Admin (Owner) in the User Management page. The owner role has the following attributes.

  • Create other users with or without administrative privileges.
  • Access billing subscription information.
  • Access to licensing information. For more information on licensing for Nutanix on-prem accounts, see Licensing.
  • Access to all features.
  • View the admin menu.
  • Perform all the read or write operations.
  • Create or edit budgets.
  • View, create, edit, or delete cost centers.
  • Restrict access to a limited number of cloud account for a user.
Note:
  • My Nutanix Account Administrators are considered as Owner in Beam.

    You can't create an owner role in Beam. However, you can create as many as three Beam owners from My Nutanix. Only My Nutanix Account Administrators have the necessary permissions to create Beam owners. For more information on My Nutanix user management, see Cloud Services Administration Guide .

  • Only My Nutanix Account Administrators or Beam Owners are able to manage billing and renewals of Beam subscription. For more information on managing billing and renewals, see Cloud Services Administration Guide .
Administrator Role

An administrator is shown as Admin in the User Management page. The administrator role has the following attributes.

  • Access to all features.
  • View the admin menu.
  • Add other users.
  • Perform all the read or write operations.
  • Create or edit budgets.
  • View, create, edit, or delete cost centers.
  • Restrict access to a limited number of cloud account for a user.
User Role

A user role is created by granting read-only or read & write permission for selected accounts.

  • An account having a user role cannot create other users.
  • An account having a user role with read-only permission can view the cost data.
  • Read-only or read & write permission can be granted on the selected Nutanix accounts.

ADFS Integration

Active Directory Federation Services (ADFS) is a Single Sign-On (SSO) solution that you can use for implementing single sign-on in Beam. To integrate ADFS with Beam, log on to your MyNutanix account, and perform the integration. See SAML Authentication for details. To log on to your Beam account using ADFS, see Logging into Xi Cloud Services as an SAML User .

User Management

You can configure the following user group types in ADFS.
  • Administrator user - Users added to this group have administrator access.
  • Beam user - Users added to this group can perform operations based on the access policy assigned by the administrator user.
Note:
  • If you are a part of the Beam user group and logging into Beam through ADFS for the first time, you will not have access to any cloud account. Contact your account administrator to get access to an account.
  • If you are a part of the administrator user group and logging into Beam through ADFS, you cannot add and delete users using the Beam user management. You can perform these actions in ADFS.
  • If you are logging into Beam through ADFS, you cannot change roles (administrator to user or user to administrator). You can perform these actions in ADFS.

Support

If you log on to Beam through ADFS, you can get access to Nutanix Support only if your MyNutanix account was used to add your Beam user account. However, if your Beam user account was not added using your MyNutanix account, you do not get access to support.

Starting Beam Free Trial

Beam is a multi-cloud cost governance SaaS product that provides a free, full-featured, 14-day trial period. During the free trial period, you can configure your Nutanix On-premises and public cloud accounts (AWS, Azure, and GCP) in Beam to evaluate the features. It takes about 15 minutes to configure your cloud accounts in Beam.

About this task

The following section describes the procedure to start a free trial.
  • If you have access to the MyNutanix account, perform Step 1 .
  • If you do not have access to the MyNutanix account, perform Step 2 .

Procedure

  1. If you have access to the MyNutanix account, do the following.
    1. Login to your MyNutanix account.
    2. In the Dashboard, scroll down to find the Beam application. Then, click Launch to open the Beam application and start your free trial.
      Figure. MyNutanix Dashboard - Launching Xi-Beam Click to enlarge
  2. If you do not have an existing MyNutanix account, do the following.
    1. Open the Beam webpage.
    2. Click Start Free Trial and fill the form that appears. Then, click Submit .
      Figure. Free Trial - Form Click to enlarge
      Your MyNutanix account gets created. Also, you will receive a verification email that contains a link for logging into the Beam application.

What to do next

You can add your Nutanix, AWS, Azure, and GCP accounts in Beam.

Onboarding Nutanix Account

You can add your Nutanix account in Beam application. The application allows you to track your cloud expenses, optimize your cloud cost, and achieve visibility into your spend.

Before you begin

Ensure that you meet the following prerequisites:
  • License ID of a Nutanix asset. Refer to Nutanix Support Portal.
  • Beam administrator access.

About this task

To add your Nutanix account in Beam, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Nutanix Accounts .
  2. Enter your License Key or Asset Serial Number .
    Figure. Add Nutanix Account Page Click to enlarge display of beam console
    Note: This step can give an error message in the following scenarios.
    • The serial number or license key is invalid.
    • The serial number is valid but does not belong to your Nutanix account.
  3. Once validated, Beam fetches the account name automatically. Optionally, update the account name.
  4. Click Save to complete.
    Note: You can set up only one Nutanix account for each Beam account.

What to do next

After you add the Nutanix account, do the following for the cluster on-boarding.
  • You must enable Pulse 4K for the clusters for which you want cost visibility. You can enable Pulse from the Prism console for the clusters that need cost visibility. The version of NCC must be 3.6.4 or higher. To enable Pulse for your cluster, see Pulse Health Monitoring and Support.
    Note:
    • Beam for Nutanix on-premises only works when Pulse is enabled.
    • There are some known data inconsistencies for clusters with AOS versions 5.10.10, 5.10.11, and 5.15. It is recommended to upgrade the AOS version to 5.15.1 or higher for cluster costing and resource level metering to work in Beam.
    • Beam recommends upgrading NCC to 3.10 to get accurate cost visibility for snapshots (Protection Domain). There are some known data inconsistencies for clusters with NCC version 4.3.0.1. Hence, it is recommended to upgrade the NCC version to 4.4.0 or higher. For more information about upgrading NCC, see Nutanix Cluster Check (NCC) Guide.
  • To view the cluster names and VM names, you must enable additional support information. To enable additional support information, see Configuring Pulse.
  • Beam supports the cost visibility for Objects and it requires the version of Prism Element to be 5.11.2 or higher and Prism Central to be 5.17.1 or higher.
Note: The cost of VM does not depend on the utilization of resources (for example, CPU, RAM, storage). It depends on the allocated resources to a VM.

Beam Gov(US) Cost Governance

Beam Gov(US) is an isolated instance running in AWS GovCloud (US) region to cater specific regulatory compliance requirements of the US government agencies at federal, state, and local levels, government contractors, educational institutes, and other US customers who run sensitive workload in AWS GovCloud and Azure Government Cloud, and want to bring Cost Governance for their cloud infrastructure, gain visibility, optimize and control their spend. Beam Gov(US) provides a single plane consolidated view for Cost Governance.

The onboarding process for Beam Gov(US) users differs from the onboarding process for commercial account users.
  • Separate Beam instance is deployed in the AWS GovCloud region (US-West) with a separate login URL for Beam Gov(US) users.
  • Beam Gov(US) supports the cost governance for AWS, Azure, GCP, and Nutanix On-premises in the GovCloud.
  • Beam Gov(US) also supports commercial cloud accounts along with the GovCloud.
Note: Beam Gov(US) Cost Governance is an early access feature. For more information, contact Nutanix Support .

Beam Gov(US) Sign up

The Beam Gov(US) sign up includes two steps.
  1. Beam Gov(US) Sign up Request Approval - The sign up request approval process involves the following steps.
    • Sign-up Request

      Contact the sales team expressing an interest in using Beam Gov(US).

    • Customer Verification

      The request is forwarded for verification to the Nutanix GovCloud Security team. As part of the verification, you will receive a form through DocuSign that you must fill and send back.

    • Beam Account Activation

      Once the request passes through the verification, Customer Service initiates the account creation process, and the primary user is notified with login details through an email. The email contains verification link, upon verifying email, the user can login to the Beam Gov(US).

  2. Account Registration Completion - In the Beam Gov(US) login page, create a password and select a timezone. Then login into the Beam console. You can enable or disable the MFA from the Profile page in the Beam console. For more information on enabling or disabling the MFA, see User Management.
Note: After you complete the sign-up steps, perform the Nutanix account onboarding. There are no changes in the onboarding steps for Beam Gov(US). For more information, see Onboarding Nutanix Account.

User Management

You can add and manage users for GovCloud using the Beam console.

You can perform the following operations in Beam Gov(US).
  • Add a user

    To go to the User Management page, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > User Management . To add a user, see Adding a Beam User.

    In the case of AWS user management, the user may have access to the commercial account but no access to the GovCloud account linked to the commercial account. To give AWS GovCloud account access to a user, you must select the GovCloud account linked to the commercial account.

    Figure. User Management - GovCloud Account Click to enlarge Access to GovCloud Account
  • Resetting Password and MFA Management
  • Configuring Single Sign-On

Resetting Password and MFA Management

You can reset your password and enable or disable MFA from the Profile page in the Beam console.

About this task

To go to the Profile page, click the user drop-down menu on the top-right corner and select Profile .

To change your password, click the Change Password link.

Figure. Profile Page - Change Password Link Click to enlarge Change password link

To enable MFA, do the following.

Procedure

  1. In the Profile page, click the Enable MFA link.

    The Enable Multi-factor Authentication page appears.

  2. Do one of the following.
    • Scan the QR code by using the virtual MFA application (Google or Microsoft Authenticator).
    • Click the secret code link to get the secret code. Enter the secret code in your virtual MFA application.
      Figure. Enable Multi-factor Authentication Page Click to enlarge Enabling MFA

      The virtual MFA application starts generating codes.

  3. Enter the codes in Code 1 and Code 2 boxes. Then click Set MFA to enable MFA.

    To disable MFA, click the Disable MFA link in the Profile page.

    In the case your MFA device is lost or not accessible, click Login via OTP (for lost MFA)? link. Beam sends an OTP to your registered email id. Enter the OTP to login to Beam.

    Figure. Beam Login Page - Lost MFA Link Click to enlarge

Configuring Single Sign-On

The following section describes how to configure the single sign-on feature for Beam Gov(US).

About this task

To configure the single sign-on feature, do the following.

Procedure

  1. Log on to the Beam Console.
  2. Click the user drop-down menu on the top-right corner and select Single Sign On .
  3. In the Single Sign On page, in the Application Id box, enter the application id.
    Note: To get the Application Id, contact Nutanix Support .

    A success message appears, displaying that the single sign-on is successfully configured.

  4. Log out from the Beam Console to go to the login page.
  5. In the Login page, click Login with Single Sign On .
  6. In the Email box, enter your email id.
    In the case of conflict, while logging through the email address, you can click Try with Application ID to login with the application id.
  7. Click Login .

    You are redirected to your organization’s single sign-on application page.

    Enter your credentials and login to Beam Gov(US).

Getting Started With Configurations

After you onboard your Nutanix accounts in Beam, the following information becomes available for you to consume:
  • Dashboard - Get a graphical view of your overall spend, spend analysis, spend overview - TCO cost heads, and spend overview - virtual machines.
  • Analyze - Provides a deep visibility into your projected and current spend and allows you to track spend across Nutanix resources both at an aggregate and granular level. You can drill down the cost further based on your Clusters, Services, Service Types, Cost Centers, and Tags (Prism Categories are considered as Tags).
The following are the configurations to perform so that you can begin controlling your Nutanix On-premises consumption:
  • Verify and update Nutanix cost - The Product Portfolio tab allows you to view all the Nutanix products purchased to date, their capacity, and assumed market prices. Beam calculates the spend data based on the assumed market prices of the Nutanix product. You can verify and reconfigure the system assumed cost of your purchased Nutanix products or licenses manually.
  • Configure the Total Cost of Ownership (TCO) model - The Cluster tab provides a list of all the clusters along with the monthly cost for each cluster. Total Cost of Ownership (TCO) of a cluster is considered as its cost across Beam. This model covers all the cost considerations of running Nutanix Enterprise Cloud in your datacenter. You can view the details of different cost heads for a specific cluster and edit the industry-specific TCO assumptions to the actual TCO inputs for your cluster.
  • Select the Resource Metering Model - The Resource Metering tab allows you to select the resource metering model for individual clusters. Resource metering provides a granular view of the cost of running a resource within a Nutanix cluster. The granular resource level costing helps in understanding the cost incurred to run a Nutanix resource that can be used for Chargeback. Resource metering is done by allocating the amortized cost of the cluster proportionally to the resources that are running in the cluster. You can select between Actual Virtual Capacity and Target Virtual Capacity models.
  • Create Business Units and Cost Centers for Chargeback – You can define a business unit by combining a group of cost centers. Chargeback is built on the business unit and cost center configuration construct that you define for the resources across all your Nutanix accounts.
  • Create Budget Alerts - A budget allows you to centralize the budget at the business unit, cost center, or scope levels to ensure that your consumption is within the budget that you have defined.

Nutanix Cost Configuration

Beam allows you to define configuration settings for your cloud cost data. Cost Configuration is a set of rules that allow you to update cost inputs manually, and also select cost presentation options, allocation model options, and reporting rules that define how the cost of cloud resources get reported in Beam.

Cost metering in Beam involves the following three step process to provide a detailed view of the existing spend on the resources based on the purchased products and deployed clusters.
  1. Cluster Costing - is where the cost of purchased Nutanix, Third-party, or OEM hardware and software is added to the Total Cost Ownership (TCO) model to calculate the monthly amortized cost of the cluster. For more details about the TCO configuration of a cluster, see the Cluster - TCO Configuration section of this user guide.
  2. Resource Metering - is where the monthly amortized cost of the cluster is split on a daily granularity to the virtual resources used within the cluster, based on their usage. For more details about resource metering and resource metering model, see the Resource Metering section of this user guide.
  3. Service Costing - is where the blended resource (such as guest VMs, Snapshots, Files, and Objects) cost is calculated by including cost of their usage and overheads such as the software cost and the hidden shared platform cost. For example, for Nutanix VM, the cost of vRAM, vStorage, and vCPU along with the amortized cost of management license (such as Prism, Flow, and Calm) and the platform (PC) are included.

Beam supports only Pulse enabled clusters. Any cluster with Pulse not enabled is considered as not onboard for Beam and is not shown in the Cluster tab. If pulse is not available due to some reason for a particular day then the cluster cost incurred for that day is known as Unmetered cluster cost

You can configure the cost for Nutanix Product Portfolio, Cluster, and Resources.

To go to the Cost Configuration page, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Nutanix Cost Configuration .

In the Nutanix Cost Configuration page, you can view the following tabs.
  • Product Portfolio - The Product Portfolio tab is a comprehensive repository of all the Nutanix products purchased to date, their capacity, and assumed market prices.
  • Cluster - The Cluster tab provides a list of all the clusters and monthly costs for each cluster. TCO model is the cost allocation basis for the clusters. You can edit the TCO details for each cluster.
  • Resource Metering - The Resource Metering tab provides a list of clusters along with the resource metering model selected for each cluster. The resource metering model allocates the amortized cost of the cluster proportionally to the resources that are running in the cluster. The proportional allocation can be based on the actual virtual capacity or target virtual capacity. You can configure the allocation type at a cluster level.

Nutanix Cost - Verify and Update

The Product Portfolio tab is a comprehensive repository of all the Nutanix products purchased to date, their capacity, and assumed market prices.

The Product Portfolio tab allows an administrator to visualize the following.
  • Filter a product by the name or view the active or expired products.
  • View the list of products that Beam considers for the cost calculations. Beam considers only the products with active terms for amortized cost calculations.
  • View the assumed costs for each product or license purchase.

In the top-right corner of the Product Portfolio tab, select the depreciation period from the Depreciation Schedule drop-down list and click Apply . The Hardware costs and any perpetual licenses are amortized based on the depreciation period you select. This impacts the amortized cost calculations within the product.

You can filter the products according to the product type (software or hardware) and product status (active or expired).

Figure. Product Portfolio Page Click to enlarge display of beam console

Configuring Nutanix Products Cost

You can reconfigure the system assumed cost of your purchased Nutanix products or licenses manually.

About this task

Beam calculates the spend data based on the assumed market prices of the Nutanix product. The spend data shown in Beam may not be the actual price that you may have paid as a Nutanix customer.
You can configure the cost in any of the following ways.
  • Inline cost editing : This option allows you to edit the cost of individual products. You can filter a subset of products using the search and individually overwrite the price with the desired price you want to use in the calculation.
    Note: In case you reconfigure the price for a line item more than once, Beam considers the latest update for all calculations.
  • Upload and Import : This option allows you to import the cost of individual Nutanix products with a Nutanix cost configuration file.

You can download the Nutanix cost configuration file (in XLS format) of the product portfolio to edit the price and terms of individual products in an offline mode. You can upload and import the cost configuration file in Beam after you update the file with the new cost and term inputs.

To configure the cost of your purchased Nutanix products, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Nutanix Cost Configuration .
    The Product Portfolio tab appears.
  2. In the Product Portfolio tab, click Configure Cost .
    The Cost Configurations page appears.

    You can select Inline cost editing or Upload and Import .

  3. If you select Inline cost editing , do the following.
    • In the Cost column, enter the new cost value for the products you want. Then click Save to save your changes.
  4. If you select Upload and Import , do the following.
    1. Click Download File to download the Nutanix cost configuration (XLS) file.
      Figure. Nutanix Cost Configuration - Upload and Import Click to enlarge
      Follow the on-screen instructions and Nutanix cost configuration guidelines to update the cost and terms in the NX_Cost_Configuration sheet of the cost configuration (XLS) file.
      Note: You can only edit the highlighted cells in the New Cost (in USD) column in the NX_Cost_Configuration sheet of the cost configuration (XLS) file.
    2. In the Cost Configurations page, click Upload and Import to upload the updated cost configuration (XLS) file in Beam.

Cluster - TCO Configuration

The Cluster tab provides a list of all the clusters along with the monthly cost for each cluster.

This section allows you to configure the TCO of a cluster. The TCO model has a default industry standard assumptions that allows you to include the cost of any non platforms by providing the true cost of running the Nutanix Enterprise Cloud in your datacenter.

You can click Edit TCO against a cluster to view the details of different cost heads for a specific cluster and edit the industry-specific TCO assumptions to the actual TCO inputs for your cluster.
Figure. TCO Configuration Click to enlarge

Total Cost of Ownership

Beam for Nutanix Enterprise Cloud using a total cost of ownership (TCO) model covers all the cost considerations of running Nutanix Enterprise Cloud in your datacenter.

TCO is a configurable financial model that allows you to analyze the direct and indirect costs of owning, operating, and maintaining the Nutanix Enterprise Cloud. To simplify the accounting of the different cost heads contributing to the total cost of running your Nutanix Enterprise Cloud, TCO provides a costing model that includes default costs and assumed (industry standard) costs. Using TCO, you can view all the assumed costs and the logic using which the cost is calculated. You can also change the assumed cost to the actual cost incurred by you.

TCO Model

The TCO model is based on the following cost data points.
  • Purchase data for Nutanix software and hardware cost associated with your Nutanix account.
  • Assumed or configured cost of the third-party software and hardware that are running as a part of your Nutanix cloud environment.
  • Assumed or configured cost (based on the number of nodes) of the datacenter infrastructure, facilities, and services required to run the Nutanix enterprise cloud.

You can click Edit TCO against a cluster to view the details of different cost heads for a specific cluster and edit the industry-specific TCO assumptions to the actual TCO inputs for your cluster.

You can add custom costs for any custom third-party software, telecom service, facilities cost, and services cost.

TCO Model - Nutanix

Table 1. Cost Heads
Cost Heads Description Amortized
Hardware
  • Nutanix Hardware Cost - Represents the cost of the Nutanix hardware appliances (NX series) that you have purchased. This cost data is pulled directly from your Nutanix account. However, you can click Edit to edit the cost of individual products.
  • Third Party Hardware Cost - Represents the cost of hardware purchased from third-party server vendors or OEM appliances. You can click Configure to enter the Average Cost per Third party server node per month .
    The third-party hardware cost is based on the following assumptions.
    • Average Price per Third-Party Server is assumed as $12,000 with a default support period of 5 years. You can edit this assumption based on your requirement.
    • The start date for third-party server is aligned with the purchase date of the Acropolis software.
  • To edit the custom RAM cost, click Edit Custom RAM Cost and enter the following details.
    • Cost Description
    • Memory Capacity
    • Cost per GiB per Month
  • Custom RAM Cost Breakup - Represents the cost break-up of physical memory (in GiB) in the overall server hardware cost. You can click Configure to enter the cost per memory capacity per month.
Cost of Nutanix hardware amortized for the depreciation period you select in the Product Portfolio tab.
Software
  • Nutanix Software Cost - Represents the cost of the Nutanix software licenses (perpetual or term-based) that you have purchased. This cost data is pulled directly from your Nutanix account. However, you can click Edit to edit the Cost and duration of individual licenses.
    Note:
    • The perpetual licenses are amortized based on the depreciation period input in the Product Portfolio tab.
    • Currently, Beam supports the following software licenses in the TCO model - Acropolis, Prism, Calm, Flow, Files, Objects, Acropolis software bundles for VDI and ROBO, Nutanix Cloud Infrastructure (NCI), Nutanix Cloud Manager (NCM), and Nutanix Unified Storage (NUS) tiers.
  • Third Party Software Cost - Represents the cost of third-party software license that you have purchased.

    The default vSphere cost is based on the following formula. The vSphere cost is included only for the clusters with ESX as the hypervisor.

    vSphere Cost = Number of Nodes * Number of Processors per Node * vSphere Licence Cost per Processor

    The number of processors per node is 2, and the number of nodes is the number of nodes that constitutes the cluster.

    To add a new third-party software cost, click Add Custom Third Party Software Cost and enter the following details.
    • Cost Description
    • Cost per License
    • Cost Type
    • Term
    • Start Date
    • Number of Licences
Cost of Nutanix software amortized for the depreciation period you select in the Product Portfolio tab for a one-time or perpetual license. The cost amortization for term software licenses is based on the term for which the license is purchased.
Facilities
  • The data center type On Premises represents the cost of facilities required to run Nutanix private cloud on an on premise datacenter.
    Note: The default assumption is that Nutanix is running on an on premise datacenter.

    You can click Configure to change the Power and Cooling Cost and Data Center Space/Infrastructure Cost .

    The PUE and Cost per KWh within the Power and Cooling cost is based on industry standard average and US standard power rate respectively. You can change the values based on your actual cost incurred and your country standards. Similarly, you can update the industry standard assumed cost for Average Rack Units per Rack and Cost per Rack per Month for DC Infrastructure/Space within Data Center Space/Infrastructure Cost .

  • The data center type Co-Location represents the cost of facilities required to run Nutanix private cloud on co-located datacenter spaces, including the assumed Custom Facilities Cost . You can click Configure to change the Co-Location Cost and add the Average Rack Units per Rack and Co-Location Cost per Rack per Month .
  • To add custom third-party facilities cost, click Add Custom Third Party Facilities Cost and enter the Cost Description and Monthly Cost Per Node .

Note: If you change the datacenter type from On premise to Co-Location, or conversely, the cost model is reset to default state of the datacenter type that you select.
Amortized cost of facilities spread over the months.
Telecom

Represents the cost of the Telecom services and Ethernet switches that you have purchased.

Ethernet Switch/Top of Rack Switch Cost - Represents the cost of the Ethernet switch or the top of rack switch used in your datacenter rack.

This calculation is based on the following formula.

Ethernet Cost/TOR = Number of Nodes * Number of Ports per Node * (Average Cost / Number of Ports per Ethernet Switch)

You can click Configure to change the assumed cost to the actual cost of Average Cost per Ethernet/TOR Switch (5 Year Support) and Number of Ports per Ethernet Switch . The change is reflected in the values for the Average Cost per Port and the Number of Nodes .

The Ethernet/Top of rack switch cost is based on the following assumptions.
  • Number of ports used per node is two.
  • Ethernet switch cost gets added based on the purchase date of the new Nutanix hardware, OEM, or third-party hardware.
To add a custom third-party telecom services cost, click Add Custom Third Party Telecom Cost and enter the following details.
  • Cost Description
  • Start Date
  • Cost Type
  • Cost to be Added
  • End Date
  • Recurring
  • One-time - Telecom cost spread over the start and end time.
  • Recurring - Telecom cost spread over a recurring period.
Services

Represents the cost of the custom services that you have purchased. Beam does not assume the cost of custom services and must enter the cost based on your actual cost.

To add a custom third-party services cost, click Add Custom Third Party Services and enter the following details.
  • Cost Description
  • Start Date
  • Cost Type
  • Cost to be Added
  • End Date
  • One-time - Services cost spread over the start and end time.
  • Recurring - Services cost spread over a recurring period.
People
Represents the cost of the administration of Nutanix nodes that you have purchased. You can click Configure to change the assumed cost to the actual cost that you have incurred on the following administration cost parameters.
  • Nutanix Administration Outsourced Percentage (Assumed value is five percent)
  • External Admin - Annual Fully Burdened FTE Rate (Assumed cost is USD 80000)

  • Internal Admin - Annual Fully Burdened FTE Rate (Assumed cost is USD 150000 based on US benchmark for IT admin salary)
  • Number of Nutanix Nodes Managed per FTE (Assumed value is 100 based on general observation)

Amortized cost of administrative staff spread over the months.

Resource Metering

The Resource Metering tab allows you to select the resource metering model for individual clusters.

Resource metering provides a granular view of the cost of running a resource within a Nutanix cluster. The granular resource-level costing helps in understanding the cost incurred to run a Nutanix resource that can be used for Showback or Chargeback.

Resource metering is based on the sunk cost allocation from the cluster level to the resource level (based on the specifications and allocation hours). You can view the list of resources in a cluster and cost associated with each of the resources at a daily or monthly granularity.

Note: The cost of a resource depends on the provisioned capacity of CPU and RAM, and actual utilization of storage.

Resource metering is done by allocating the amortized cost of the cluster proportionally to the resources that are running in the cluster.

The following are the available types of resource metering model.
  • Actual Virtual Capacity - The amortized cluster cost is split to the resources based on the actual provisioned virtual capacity (vCPU, vRAM, and vStorage).
  • Target Virtual Capacity - The amortized cluster cost is split to the resources based on the target provisioned virtual capacity based on the overcommit ratio (vCPU : pCPU, vRAM : pRAM, and vStorage : pStorage).
For more information, see Resource Metering Model.

You can change the Resource Metering Model from the Clusters table. In the Resource Metering Model column, click the drop-down list and select the metering model you want for the cluster. Then click Save to apply the selected metering model to the cluster.

Figure. Selecting Resource Metering Model Click to enlarge Selecting Resource Metering Model

You can also edit the overcommit ratio for the Target Virtual Capacity model. Click Edit against the cluster for which you want to change the overcommit ratio. In the Target Virtual Capacity - Overcommit Ratio page, enter the new ratio and click Done . Then click Save to save the changes.

Resource Metering Model

The Resource Metering Model allocates the cluster cost to the Nutanix resources within the cluster. There are two types of Resource Metering Model - Actual Virtual Capacity and Target Virtual Capacity .

Actual Virtual Capacity

The Actual Virtual Capacity model allows you to split the cluster cost to the resources based on the actual provisioned virtual capacity (vCPU, vRAM, and vStorage).

The cost of a cluster gets divided between the cluster raw CPU cores and the raw total cluster flash drive capacity in tebibytes (TiBs) based on the Nutanix Acropolis capacity-based licensing ratio. The cost of the cluster raw CPU cores gets fully allocated to n vCPUs in the cluster based on vCPU-hours ( n is the number of vCPUs). The cost of the cluster RAM (in GiB) gets fully allocated to n vRAMs in the cluster based on vRAM-hours ( n is the number of vRAMs). The cost of the raw total cluster flash drive capacity in tebibytes (TiBs) gets fully allocated to m vDisk in the cluster based on vDisk-hours ( m is the vDisk capacity).

This allocation logic helps you to get the cost of 1 vCPU-hour, 1 GiB of vRAM-hour, and 1 GiB of vDisk-hour. The cost of a resource is derived by using these two variables, specification (vCPU, vRAM, storage allocation), and allocated hours.

Target Virtual Capacity

The Target Virtual Capacity model allocates the cluster cost to the resources based on the target provisioned virtual capacity based on the overcommit ratio (vCPU : pCPU, vRAM : pRAM, and vStorage : pStorage).

The cost of a cluster gets divided between the cluster CPU cores, RAM (in GiB), and the flash drive capacity in tebibytes (TiBs) based on the overcommit ratio. The vRAM : pRAM is assumed to be 1:1, and is not configurable.

The cost of the cluster CPU cores gets fully allocated to expected vCPUs in the cluster based on vCPU-hours (expected vCPU = actual pCPU * expected vCPU overcommit). The cost of the cluster RAM gets fully allocated to expected vRAMs in the cluster based on vRAM-hours (expected vRAM = actual pRAM * expected vRAM overcommit). The cost of the cluster flash drive capacity in tebibytes (TiBs) gets fully allocated to expected vStorage in the cluster based on vDisk-hours (expected vStorage = actual pStorage * expected vStorage overcommit).

The difference between planned vCore, vRAM, or vStorage versus actual vCore, vRAM, or vStorage is shown as Unprovisioned Virtual Capacity or Overprovisioned Virtual Capacity in the VM Name column of the VM details table in the Resource Metering tab.
Note:
  • Unprovisioned virtual capacity - When the planned virtual capacity is greater than actual virtual capacity.
  • Overprovisioned virtual capacity - When the planned virtual capacity is less than actual virtual capacity.

In the overprovisioned virtual capacity scenario, the cluster cost from the sum of all the resource cost is higher than the cluster amortized cost. You can view this information in the VM details table in the Resource Metering tab.

Outage Scenarios

This section provides a list of the outage scenarios that can occur and the method by which Beam visualizes Resource Metering.

  • Cluster node outage - Beam calculates the Resource Metering based on the best or last available cluster configuration. The best available data is either the current day cluster configuration or the last known complete cluster configuration.
  • Cluster outage - Beam ignores the cluster configuration for the current date and takes the latest or last available cluster configuration for the Resource Metering.
  • Pulse disablement - Beam calculates the number of days from the current day until the last available data point. If the difference is more than 15 days, Beam considers the cluster to be Pulse disabled for the current month.
  • VM outage - Beam ignores the resource configuration for the current date and takes the latest or last available resource configuration for the Resource Metering.
  • VM deletion during pulse outage - Beam keeps using the last known available resource configuration until the pulse outage crosses a threshold of 15 days. After the pulse outage crosses the threshold, Beam considers the resource to be deleted.
  • Pulse outage - Beam ignores the cluster configuration for the current date and takes the latest or last available cluster or resource configuration for the Resource Metering.

Currency Configuration

Configure currency to view the cloud spend in your preferred currency.

The currency configuration reduces the ambiguity in analyzing cloud spend from different cloud providers who often provide billing data in different currencies. For example, GCP might report cloud consumption in INR while AWS report cloud consumption in USD. Consolidating the billing data from these different sources without considering currency type results in ambiguous reports and dashboards. In order to simplify multicloud cost governance, Beam allows you to configure a single currency to calculate spend data across all views. You can also configure the corresponding conversion rates for the configured currency or use dynamic rates that Beam provides.

Source currency

Source currency is the currency that your cloud service provider reports billing. When you onboard multiple cloud billing accounts from different cloud providers or regions, you can see a consolidated list of all the source currencies in the respective billing data on the Currency Configuration page. If you onboard a GCP billing account reported in INR and an AWS payer account reported in USD, you will see INR and USD in the source currency list.

Target currency

Target currency is the preferred functional currency for your organization to view spend analysis across Beam in. All the spend data shown in Beam is also converted to this currency. Beam uses the target currency to provide a unified cost view when you onboard multiple cloud accounts with different source currencies. Furthermore, this configuration gives you the flexibility to set a single currency for the following views.
  • Multicloud views such as All-Clouds , Financial (Business Unit or Cost Center), or Scopes
  • Cloud overviews such as GCP Overview , AWS Overview , or Azure Overview

Currency conversion

When you select target currency, you must also select the conversion rates applicable for the selected currency. Beam supports the following currency conversion types.
  • Dynamic Currency Conversion : Beam uses the third-party API from https://exchangeratesapi.io/ to ingest the conversion rates for the corresponding source currencies.
    Note: Beam uses the conversion rate for the first of every month to calculate spend for the entire month. If the conversion rate for the first of every month is unavailable, Beam uses the last fetched monthly rates to calculate spend for that month.
  • Custom Defined Currency Conversion : Beam uses the user-defined exchange rate to calculate historic and projected spend data across all days/months/years.

Configuring Currency and Conversion Rates

You can use this configuration to select the target currency and the corresponding conversion rates applicable for spend analysis across Beam.

About this task

After you configure target currency, you see the following across Beam.
  • Spend data in the target currency for all cloud overview and mulitcloud views.
  • A currency toggle to select between source currency and target currency for individual cloud accounts.
For more information on general guidelines and considerations, see Currency Configuration Considerations .

To configure the currency, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu and then go to Configure > Currency .
    The Currency Configuration page appears.
    Figure. Configure Currency Click to enlarge
  2. Click View Source Currencies to view the list of source currencies corresponding to the cloud resource billing data.
  3. Under Target Currency , select the preferred currency in the drop-down list.
    For example, if you select AMD Armenian Dram , costs across Beam reports in AMD.
  4. In the Currency Conversion area, do one of the following to configure the conversion rates applicable for the selected currency.
    • To automatically fetch the currency exchange rates, click Dynamic Currency Conversion . Additionally, click View to see the ingested exchange rates for the last 12 months.
      Note: Currency exchange rates are updated by Nutanix on a monthly basis. Currency exchange rates are provided as estimates and for informational purposes only. The rates and conversion estimates should not be relied on for invoiced billing conversions by cloud service providers.
      Click to enlarge
    • To manually define the currency exchange rates, click Custom Defined Currency Conversion and then click Customize .

      In the text box, enter the exchange rates as shown in the following figure.

      Click to enlarge
  5. Click Save to apply the currency configuration.
    The configured currency applies to all the available views in Beam.

Currency Configuration Considerations

Limitations and guidelines to consider when using the currency configuration.

Dashboard

  • The Reserved Instances widget on the Dashboad always reports with source currency across all AWS and Azure views.
  • By default, Beam provides the spend data in the target currency.
  • The currency toggle is available when you select individual cloud accounts in the view selector.
  • The currency toggle is not available when you select cloud overview or multicloud views in the view selector.
  • The currency toggle is not available when the configured target currency is same as the source currency.

Analyze

  • By default, Beam provides the spend data in the target currency.
  • The currency toggle is available when you select individual cloud accounts in the view selector.
  • The currency toggle is not available when you select cloud overview or multicloud views in the view selector.
  • The currency toggle is not available when the configured target currency is same as the source currency.
  • The reports in the Analyze page is in the currency that is selected at the time of report generation.
    • If you select source currency in the toggle, and then click download, share, or schedule, the reports are in the source currency.
    • If you select target currency in the toggle, and then click download, share, or schedule, the reports are in the configured target currency.
      Note: If you modify the target currency after scheduling the reports, Beam always uses the target currency that is configured at the time of generating the schedule reports. For example, if the target currency is INR while scheduling the reports. And you modify the target currency as GBP, then Beam generates the scheduled reports in GBP.
    • If the currency toggle is not available, the reports you download, share, or schedule are in the configured target currency.

Chargeback

  • By default, Beam provides the spend data in the target currency. The currency toggle is not available in Chargeback .
  • The system report (Global Chargeback Report) that you can download, share, or schedule is in target currency that is configured at the time of report generation.

Budget

  • By default, Beam provides the spend data in the target currency. The currency toggle is not available in Budget .
  • Beam shows the allocated cost of the budget in the target currency.

Reports

  • System reports are in target currency that is configured at the time of report generation. If the target currency configuration is INR and you modify the target currency to GBP after 4 weeks. The system reports generated weekly are in INR for week 1, week 2, week 3, and week 4. The system reports generated for week 5 are in GBP as the target currency at the time of report generation is GBP.
    Note: The following reports are in source currency.
    • Daily reports: New EC2 RI Recommendation report and EC2 RI Utilization Report
    • Monthly reports: Expired RI Report , Expiring RI Summary Report , and On Demand vs Reserved Hours Cost
  • The currency in the Custom reports is based on the configuration in the create or edit page. The reports are in either source currency or target currency as configured while creating the reports.

Save

  • By default, Beam provides the spend data in the target currency.
  • The currency toggle is available when you select individual cloud accounts in the view selector.
  • The currency toggle is not available when you select cloud overview or multicloud views in the view selector.
  • The currency toggle is not available when the configured target currency is same as the source currency.
  • The system report (Cost Optimization Detailed Report) that you can download, share, or schedule in the Save page is in target currency that is configured at the time of report generation.
  • The drill-down reports that you can download, share, or schedule in any of the tabs on the Save page uses the selection in the currency toggle.
    • If you select source currency in the toggle, and then click download, share, or schedule, the reports are in the source currency.
    • If you select target currency in the toggle, and then click download, share, or schedule, the reports are in the configured target currency.
    • If the currency toggle is not available, the reports you download, share, or schedule are in the configured target currency.
    Figure. Save Click to enlarge

Purchase

Beam uses the source currency provided in the billing data for assessing reserved instances and displays the data in source currrency. Beam does not use the target currency provided in the currency configuration page for assessing reserved instances.

Cloud Account Onboarding

  • When you onboard your first cloud account, Beam configures the source currency as the default target currency with Dynamic Currency Conversion rates.
  • When you onboard a cloud account with new currency and the currency conversion is Custom Defined Currency Conversion . Beam adds the the latest dynamic rate as a custom rate for the new currency.

Dashboard (Nutanix)

The dashboard for Nutanix displays informational widgets for ease of cost governance.

To view the Nutanix dashboard, log on the Beam console and select any of the connected Nutanix accounts.

Nutanix dashboard displays the following widgets.
Note: Beam provides a toggle to view spend data in your preferred currency. You can select the currency toggle at the top right to switch between target and source currency. For information on general guidelines and considerations, see Currency Configuration Considerations .

Spend Overview

This widget shows the Month to date, the amortized cost for Nutanix software you have purchased. This gives you a high-level view of the ongoing costs of running your Nutanix on-premises private cloud. In a multi-cloud context, it helps you to get a sense of the run-rate costs of using the private-cloud, similar to a public cloud ongoing spend view. By default, this widget displays the top spend of the top five clusters or services in your Nutanix account.

Figure. Dashboard - Spend Overview Click to enlarge Spend overview of Nutanix clusters

Spend Analysis

The Spend Analysis widget displays a bar graph of the historical spend analysis for the selected period with the current and projected spend for the past few months.

By default, this view displays the monthly spend data for the clusters. You can change the default view to display daily projections. To view a detailed information, click View Spend Trend , which redirects you to the Analyze page.
Figure. Dashboard - Spend Analysis Click to enlarge Spend analysis of Nutanix clusters

Spend Overview - TCO Cost Heads

This widget shows the total cost incurred for all the onboarded clusters. You can view the cost breakups for all the cost heads (for example, software, telecom, hardware, and so on). You can hover over the chart to view the contribution of each cost head (in percentage) to the total spend.

To view a detailed information, click View Details , which redirects you to the Resource Metering tab in the Analyze page. Resource metering provides a granular view of the cost of running a resource within a Nutanix cluster. The granular resource-level costing helps in understanding the cost incurred to run a Nutanix resource that can be used for Showback or Chargeback.

Figure. Dashboard - TCO Cost Heads Click to enlarge

Spend Overview - Virtual Machines

This widgets shows the cost incurred (Month to date) for all the VMs and VM-Snapshots that are running in your clusters.

You can click View All , which redirects you to the Compute view for detailed information that includes: total spend overview, the cost for all the sub-services, VM IDs, and cost based on categories applied to the Nutanix resources.

Figure. Dashboard - Virtual Machines Spend Click to enlarge

Cost Analysis (Nutanix)

Beam provides a detailed view of the existing spend on Nutanix resources based on the deployed clusters and purchased products.

The Analyze page allows you to track spend across Nutanix resources both at an aggregate and granular level. You can drill down the cost further based on your clusters, VMs, and Tags (Prism Categories are considered as Tags).

Figure. Analyze Click to enlarge

Analyze views help you with the following.

  • Graphical and tabular view of spend data. The top portion of the Analyze page displays a graphical view of your data. The bottom portion of the Analyze page displays a tabular view of your spend data.
    Note:
    • By default, each view displays values in a line chart form. You can change the default view to a pie chart or bar graph.
    • The spend data for current day can be delayed by 24 hours.
    • Beam displays the date and time it last updated the spend data at the top-right corner of the Analyze view. Beam updates spend data every 6 hours. However, Beam skips updating, if the data ingested from the cloud providers is the same since the last update.
  • Deep visibility into your historical, current, and projected spend based on the time period selected. You can select the time period between Day or Month at the top-right of the chart.
  • Customize the view of your spend data according to the selected filter options. To create a filter, you can select the required options under Filters and click Apply .
  • Schedule, share, and download customized reports under each view.
  • Cumulative spend analysis. To visualize the cumulative spend data, you can turn on the Cumulative toggle.
  • Spend data in your preferred currency . You can select the currency toggle at the top right to switch between target and source currency. For more information on general guidelines and considerations, see Currency Configuration Considerations .

The Analyze page contains the following sub-tabs.

  • Current Spend
  • Projected Spend
  • Resource Metering
  • Compute
  • Storage
Current Spend
The current spend view provides the current cluster cost and its breakdown based on the usage and resource data.
Table 1. Current Spend
View Description
Overview Displays the total cluster spend.
Clusters Displays the total cost of each cluster in your Nutanix account.
Service Types Displays the total cost for all the services types such as compute, storage, and no service in your Nutanix account.
Services Displays the total cost for all the services in your Nutanix account.
Cost Centers Displays the total spend split by Beam cost centers. This view includes the unallocated costs that are not tagged in your Nutanix account.
Tags Displays the current spend based on the category applied to your Nutanix resources. Click the Tags drop-down list to select a category.
Note: The chart also displays all the values that are tagged to a selected tag key.
Note: Both No Service and No Service Type include the spend of unprovisioned capacity and unmetered cluster cost.
Projected Spend
The projected spend view provides an insight into the actual and projected cost for the selected period.
Note: The projected cost is based on the amortized cost of the clusters and does not consider the actual utilization of the cluster.
How Spend Projection Works

Beam calculates the monthly amortized costs of clusters on the basis of Total Cost of Ownership (TCO). This monthly amortized cost data is also used in projecting future month's cost data. When the hardware or software scale-up or scale-down occurs or when TCO inputs are updated, Beam recalculates the monthly amortized cluster costs and updates the forecast accordingly.

Table 2. Projected Spend
View Description
Overview Displays a line chart of the projected and actual spend for the selected period.
Clusters Displays a line chart of the projected and actual spend for all the clusters in your Nutanix account.
Resource Metering
The Resource Metering view provides a granular view of the cost of running the resources such as VM, VM-Snapshot, Files, and Objects within a Nutanix cluster. The granular level costing helps in understanding the cost incurred to run a Nutanix resource that can be used for Showback or Chargeback.

The Resource Metering tab displays the list of clusters and cost associated with each of the clusters.

  • Cluster Details - Shows the list of all clusters (excluding Prism Central Logical clusters) along with the latest or last known configuration metadata and cumulative daily amortized cost for the selected period.
    Figure. Cluster Details Widget Click to enlarge Cluster Details

    Click View Details to view the individual cluster data for the selected month. At the top-right corner, you can click the share , schedule , and download icon respectively to share, schedule, and download the report with all details of the respective cluster.

    Figure. List of resources in a Cluster Click to enlarge List of resources

You can view the following widgets.

Total Cost of Ownership - Shows the total cost incurred for the cluster. You can view the cost breakups for all the cost heads (for example, software, telecom, hardware, service, people, and facilities). You can hover over the chart to view the contribution of each cost head (in percentage) to the total spend.

Cluster Details - Shows the detailed information of the cluster. For example, resource metering model, the name of the hypervisor, user VM count, and used VM snapshot storage, used file storage, and used object storage.

List of VMs, VM-Snapshots, and Files & Objects - By default, the list of VMs running within a cluster are displayed. You can click the drop-down list in the right corner to view the cost of storage consumed by VM-Snapshots, and Files & Objects. Depending on the resource type you selected, you can view the metered cost for VMs, VM-Snapshots, Files and Objects based on usage and price per unit on a daily basis.

Table 3. List of Resources and Entities
Resources Entity Description
VM VM Name The name of the Nutanix VM.
VM ID The unique identifier of the Nutanix VM.
vCPU-hrs The aggregate of vCPU configuration and the number of hours the VM has been powered on for the selected month.
Average price per vCPU-hr The average daily cost per vCPU-hrs for the selected month to date.
vRAM-hrs The aggregate of provisioned vRAM configuration and the number of hours the VM has been powered on for the selected month.
Average price per vRAM-hr The average daily cost per vRAM-hrs for the selected month to date.
vStorage-GiB The average daily utilization of storage per VM.
Cumulative price per vStorage-GiB The total cost of storage utilization per VM for the selected month to date.
Cost (Month-to-date) The cumulative cost of VM per day for the selected time period.
Avg Cost per Hour The average cost of VM per hour for the selected month to date.
VM-Snapshots PD Name The name of the Snapshot/Protected Domain.
vStorage-GiB The average daily utilization of storage per Snapshot/Protected Domain.
Cumulative price per vStorage-GiB The total cost of storage utilization per Snapshot/Protected Domain for the selected month to date.
Cost (Month-to-date) The cumulative cost of Snapshot/Protected Domain per day for the selected time period.
Files & Objects Service Name The name of the File Service or Object Service.
vStorage-GiB The average daily utilization of storage per Files service and Objects service.
Cumulative price per vStorage-GiB The total cost of storage utilization per Files service and Objects service for the selected month to date.
Cost (Month-to-date) The cumulative cost of Files service and Objects service per day for the selected time period.
Unprovisioned Virtual Capacity
When the planned virtual capacity (such as vCore, vRAM, or vStorage) is greater than actual virtual capacity.
Overprovisioned Virtual Capacity
When the planned virtual capacity (such as vCore, vRAM, or vStorage) is less than actual virtual capacity.

In the overprovisioned virtual capacity scenario, the cluster cost from the sum of all the resource cost is higher than the cluster amortized cost. You can view this information in the VM details table.

Unmetered Cluster Cost
Unmetered Cluster Cost tracks days when the pulse was not available and shows the cluster cost incurred for those days. The Resource metering is not available when the pulse is disabled. This line item appears for each cluster corresponding to the days in the month when the pulse was disabled or unavailable.
Figure. Overprovisioned/Unprovisioned Virtual Capacity and Unmetered Cluster Cost Click to enlarge

Compute
The Compute view provides the cost specific to all the Compute Services and Sub Services that are running in your Nutanix clusters.
Table 4. Compute
View Description
Overview Displays a line chart of the total spend for all the compute services within the cluster for the selected period. You can hover over the stacked bar to view the total spend for a specific day.
Clusters Displays a line chart of the total cost of each cluster in your Nutanix account.
Services Displays a line chart of the total cost for all the compute services within your Nutanix cluster.
Sub Services Displays a line chart of the total cost for all the sub-services within your Nutanix cluster.

Beam provides cost visibility to the Nutanix Virtual Machine Service. This service has VM and VM-Snapshot Sub-Services.

Cost Centers Displays the total spend split by Beam cost centers. This view includes the unallocated costs that are not tagged in your Nutanix account.
Resources

Displays all the VM IDs (VM Sub Service) and protection domains (VM-Snapshot Sub Service) along with their associated cost.

Tags
Displays a line chart of the total cost based on the categories applied to your Nutanix resources. You can click the tag drop-down list to select a category.
Note: The chart also displays all the values that are tagged to a selected tag key.
Storage
The Storage view provides the cost specific to all the Nutanix services used for storage that are running within your clusters.
Table 5. Storage
View Description
Overview Displays a line chart of the total spend on all the services used for storage within the cluster for the selected period.
Clusters Displays a line chart of the total cost of each cluster in your Nutanix account.
Services Displays a line chart of the total cost for all the storage services within your Nutanix cluster.
Cost Centers Displays the total spend split by Beam cost centers. This view includes the unallocated costs that are not tagged in your Nutanix account.

Beam Service Categorization - Nutanix

The cost details for the following services, service types, and sub-services are shown in Beam.
Table 1. Service categorization
Category Description
Services Nutanix Virtual Machine Includes all the user VMs along with their Snapshots in the cluster.
Nutanix Files Includes all the Files services in the cluster.
Nutanix Objects Includes all the Object services in the cluster.
Nutanix End Users Includes all the user VMs hosting VDIs in the cluster running an Acropolis VDI software package.
Nutanix Edge Include all the user VMs hosting ROBO in the cluster running an Acropolis ROBO software package.
Service Types Compute Includes all the compute services running in the Nutanix cluster
Storage Includes all the storage services running in the Nutanix cluster
No Service Includes both the Unmetered Cluster Cost and Unprovisioned Virtual Capacity. For more details, refer to the section Resource Metering in the topic Cost Analysis (Nutanix) .
Sub-Services Nutanix Virtual Machine Includes all the user VMs in the cluster.
Nutanix VM-Snapshot (Protection Domain) VMs are replicated through Snapshots, which consume virtual storage capacity. The VM-Snapshot sub-service provides cost visibility of Snapshots within a cluster at a Protection Domain granularity. A protection domain is a defined group of VM snapshots to be backed up locally on a cluster or replicated on the same schedule to one or more remote sites.
Note: Beam recommends upgrading NCC to 3.10 to get accurate cost visibility for snapshots (Protection Domain).
Nutanix Edge Virtual Machine Include all the user VMs hosting ROBO in the cluster running an Acropolis ROBO software package.
Nutanix Edge Snapshot Include all the user VM-Snapshots hosting ROBO in the cluster at a Protection Domain granularity running an Acropolis ROBO software package.
Nutanix End Users Virtual Machine Includes all the user VMs hosting VDIs in the cluster running an Acropolis VDI software package.
Nutanix End Users Shapshot Include all the user VM-Snapshots hosting VDIs in the cluster at a Protection Domain granularity running an Acropolis VDI software package.
Beam associates Prism categories (Tags) to the Protection Domains if there is one VM to one PD mapping since PDs by themselves do not support tagging through Prism Categories. This helps in the following:
  • Allow Beam to filter costs by using tags that are attached to the VMs and PDs.
  • In the Cost Center definition, when a prism category is selected, both the VMs and PDs are allocated to the defined cost center.

Cost Reports

Beam generates a report to track cost consumption across all your Nutanix accounts. The report contains detailed spend information for clusters including spend at a VM level within each cluster.

The Cost Report by Cluster report is generated automatically and available to download from the Beam console. This report contains month to date detailed spend information about the VMs within the cluster.
Note: The currency used in the Cost Report by Cluster report is based on the target currency configured at the time of report generation.

Report Options

Click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports .
  • In the System tab, you can view the report. Clicking View All displays a table that contains the clusters and its associated cost. The cost column reflects the target currency using which the reports are generated. You can share, schedule, and download the report for each cluster.
    Figure. Nutanix Cost Report - Download Click to enlarge
  • In the Scheduled tab, you can view all the schedule reports. You can edit, disable, or delete any scheduled report.

Scheduling Reports

Beam application generates reports to track cost consumption for your Nutanix cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications.

About this task

The application allows you to schedule a report at a desired time.

To schedule a report, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports .
    The System tab appears.
  2. Click View All in the top-right corner of the Cost Report by Cluster to display a table that contains the clusters and its associated cost.
  3. Click Schedule (on the right corner of each row) for which you want to schedule the report sharing.
    The Schedule Report Sharing window appears.
  4. In the Report Name field, enter the name for the report you want to share.
  5. Hover over any of the Daily , Weekly , or Monthly to set the delivery schedule.
  6. In the Repeat Days field, click the days on which the you need the report to be shared.
  7. In the At and Timezone drop-down list, select the time (Hour, Minute, and AM/PM) and timezone.
  8. In the Recipients box, type the email address of the recipient to whom you want to share the report.
  9. Press Enter or Space to add the recipient email address. You can also add multiple email address separated by a comma or semicolon.
  10. If you want send a copy of the report to yourself, select the Send a copy to myself check-box and click Schedule .
    All the schedule reports are available under the Reports > Scheduled . You can edit, disable, or delete any scheduled report.

Sharing Reports

Beam application generates reports to track cost consumption for your Nutanix cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications.

About this task

Beam allows you to share the report with stakeholders over email.

To share the report, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports .
    The System tab appears.
  2. Click View All in the top-right corner of the Cost Report by Cluster to display a table that contains the clusters and its associated cost.
  3. Click Share (on the right corner of each row) for which you want to share the report.
    The Share Report window appears.
  4. In the Recipients box, type the email address of the recipient to whom you want to share the report.
  5. Press Enter or Space to add the recipient email address. You can also add multiple email address separated by a comma or semicolon.
  6. In the Report Name field, enter the name for the report you want to share.
  7. (Optional) In the Message field, enter any additional message that you want to share with the recipient along with the report.
  8. If you want send a copy of the report to yourself, select the Send a copy to myself check-box and click Share to complete.

Downloading Reports

Beam application generates reports to track cost consumption for your Nutanix cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications.

About this task

The application allows you to download the report for offline consumption.

To download a report, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports .
    The System tab appears.
  2. Click View All in the top-right corner of the Cost Report by Cluster to display a table that contains the clusters and its associated cost.
  3. Click Download (on the right corner of each row) for which you want to download the report.
    The report is downloaded to your local system.

Chargeback

The Chargeback feature enables the financial control of your cloud spends by providing the ability to allocate cloud resources to departments based on definitions. It provides a consolidated view across all your cloud accounts in a single pane of finance view.

Note the following points when creating a chargeback for your Nutanix on-premises environment.

  • The parent account is equivalent to the Nutanix account.
  • The child account is equivalent to clusters.
  • The tags are equivalent to the category. For more information on Prism categories, see Category Management.
Note:
  • Chargeback is built on the business unit and cost center configuration construct that you define for the resources across all your cloud accounts.
  • You cannot build chargeback on the custom scope. You define a scope using accounts and resources and can add a resource across different scopes.
  • You can view the spend data in the configured target currency . For more information on general guidelines and considerations, see Currency Configuration Considerations .

Business Units

A business unit is defined as a collection of cost centers. You can use the business units to define hierarchies in your organization between different departments. It is not necessary to define a business unit to view chargeback. You can also define chargeback only based on cost centers.

Cost Center

A cost center is a collection of resources within a single or multiple cloud accounts. You can assign the resources to the cost center based on tags. You can either allocate a complete account or resources within an account to a cost center.

Note:
  • If a cloud account is assigned to a cost center with the tag definition as All Tags , then you cannot share this account with another cost center.
  • An account, cluster, or a tag once used in a Cost Center definition cannot be reused. This is to prevent double-counting of the cost of resources.
  • The resources that do not belong to any of the cost centers are grouped under Unallocated Resources . You can manually allocate any unallocated resources into a cost center.

Unallocated Resources

Unallocated resources are the resources that do not belong to any of the cost centers based on definitions.

Unallocated resources include the following.

  • Accounts not allocated to any cost center (includes all the resources within the account)
  • Resources within an account not allocated to any cost center.

Multicloud Configurations

You can define a cost center based on accounts, clusters, and prism categories. You can add resources belonging to a single or multiple accoounts when defining the cost center. Beam also allows you to extend the definition of your cost centers to public clouds, that is, you can add AWS and Azure resources.

Note: Beam associates Prism categories (Tags) to the Protection Domains if there is one VM to one PD mapping since PDs by themselves do not support tagging through Prism Categories

The following image describes an example of a multicloud configuration. The cost center consists of Nutanix, AWS, and Azure resources.

Figure. Multicloud Configuration Click to enlarge

Adding a Business Unit

Before you begin

You can create a business unit only if you have an Admin role in Beam.

About this task

You can define a business unit by combining a group of cost centers. Chargeback is built on the business unit and cost center configuration construct that you define for the resources across all your cloud accounts. You can select the owners and viewers for the business unit. Both owners and viewers have read-only access to the business unit.

To add a business unit, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Chargeback .
  2. In the Business Unit Configuration page, click the Create list and select Business Unit .
    The Create Business Unit page appears.
  3. In the Name box, enter a name for the business unit.
  4. In the Owners list, click to select owners for the business unit you are creating.
    Note: The business unit owner is financially accountable for the business unit. You can select multiple owners for the business unit.
  5. In the Viewers list, click to select viewers for the business unit you are creating.
  6. In the Cost Centers list, select the cost centers that you want to map to your business unit.
  7. Click Save Business Unit to complete.
    The business unit you just created appears in the Business Unit Configuration page. You can use the business unit to build chargeback.

Editing a Business Unit

You can edit (or delete) an existing business unit.

Before you begin

You can edit or delete a business unit only if you have an Admin role in Beam.

About this task

You can define a business unit by combining a group of cost centers. Chargeback is built on the business unit and cost center configuration construct that you define for the resources across all your cloud accounts.

To edit a business unit, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Chargeback .
    You can view the list of business units in the Business Unit configuration page. You can use the drop-down to filter the list by the business unit.
  2. Click Edit against the business unit that you want to edit.
    The Edit Business Unit page appears.
  3. Click Save Business Unit after you edit the fields according to your requirement.
    Once edited, it takes 24 to 48 hours for the cost data to get updated in the Budget page.

Adding a Cost Center

Before you begin

You can create a cost center only if you have an Admin role in Beam.

About this task

A cost center is a department to which you can allocate cloud accounts and resources based on the definition. You can define a cost center by selecting resources by accounts and tags across different clouds. You can select the owners and viewers for the cost center. Both owners and viewers have read-only access to the cost center.

Note the following points when creating a cost center for your Nutanix cloud.

  • The parent account is equivalent to the Nutanix account.
  • The sub account is equivalent to a cluster.
  • The tags are equivalent to the category. For more information on Prism categories, see Category Management.
Note: Configuring Prism Categories and mapping them to specific VMs is required to create tag-based Cost Centers. Without Prism Categories, Cost Centers can be created only by mapping an entire Cluster.

To add a cost center, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Chargeback .
  2. In the Business Unit configuration page, click the Create list and select Cost Center .
    The Create Cost Center page appears.
  3. In the Name box, enter a name for the cost center.
  4. In the Owners list, click to select owners for the cost center you are creating.
    Note: The cost center owner is financially accountable for the cost center. You can select multiple owners for the cost center.
  5. In the Viewers list, click to select viewers for the cost center you are creating.
  6. Click Define Cost Center to open the Define Cost Center page.
    You define the cost center by selecting the accounts and tags across different clouds.
  7. In the Define Cost Center page, do the following.
    1. In the Cloud list, select Nutanix .
    2. In the Parent Account list, select the parent account.
    3. In the Sub Accounts list, select the sub accounts. You can select multiple sub accounts.
    4. In the Tag Pair area, select the key and value pairs to further refine the definition of your cost center. You can click the plus icon to add more key and value pairs.
      Note:
      • The resources that are not tagged to any cost center are considered as untagged. You can select and assign the value pair UNTAGGED to the respective key set in order to assign the untagged resources to the cost center.
      • For the selected resource in your Nutanix account, you can tag multiple values to a single tag key set.
    5. Click Save Filter to save the filter. You can click Add Filter to add more filters.
    6. Click Save Definition to save your cost center definition and close the Define Cost Center page.
  8. Click Save Cost Center to complete.
    It may take up to 24 to 48 hours for the cost data related to the newly added cost center to get displayed in the Budget tab.

Editing a Cost Center

Beam allows you to edit (or delete) an existing cost center.

Before you begin

You can edit a cost center only if you have an Admin role in Beam.

About this task

A cost center is a department to which you can allocate cloud accounts and resources based on the definition. You can define a cost center by selecting resources by accounts and tags across different clouds.

To edit a cost center for multicloud accounts, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Chargeback .
    You can view the list of cost centers in the Business Unit configuration page. You can use the drop-down list in the top-right corner to filter the list by the cost center.
  2. Click Edit against the cost center that you want to edit.
    The Edit Cost Center page appears.
  3. Click Save Cost Center after you edit the fields according to your requirement.

Allocating Unallocated Resources To Cost Center

Before you begin

You can allocate an unallocated resource only if you have an Admin role in Beam.

About this task

Unallocated resources are the resources that do not belong to any of the cost centers based on definitions.

To allocate an unallocated resource for chargeback, do the following.

Procedure

  1. In the Beam console, select Finance from the View Selector pop-up and go the Chargeback page using the Hamburger icon in the top-left corner.
  2. In the top-right corner of the page, click the Unallocated button.
  3. In the Unallocated Cost table, click the expand icon against the account or subscription to view the list of services.
  4. Click View Details against the service item to view the list of resources.
  5. Click the Allocate button against the resource item that you want to allocate to a cost center.
    The Select a cost center pop-up window appears.
  6. In the Cost Center Name list, select the cost center for the resource.
  7. In the Percentage Split box, enter the resource cost percentage you want to allocate to the cost center you selected.
    If you want to split the cost of the resource between two or more cost centers, click Add a split to specify the cost centers and the percentage of cost split between the cost centers.
  8. Click Allocate Resource to complete.
    The resource you just allocated appears in Allocated Cost table.

Chargeback Views

Chargeback View (Administrator)

An administrator can do the following.

  • Assign unallocated resources to a cost center
  • Create a business unit and cost center

You can select the Allocated and Unallocated options in the top-right corner of the page to view the cost details for allocated and unallocated resources.

In the Unallocated Cost table, you can use the Allocate button to allocate resources to a cost center. To allocate the unallocated resources to cost centers, see Allocating Unallocated Resources To Cost Center.

In the Allocated Cost table, an administrator can browse through all the business units and cost centers (created by the administrator) to view detailed information.

Figure. Chargeback Click to enlarge Chargeback - Global View
Table 1. Chargeback Views (Administrator)
View Description
Spend Overview Displays a pie graph of the cost breakup summary for the allocated and unallocated resources.
Spend Analysis - Unallocated Cost

Displays a bar graph of the historical spend analysis for the unallocated resources with an actual and projected spend for the last three months.

Spend Analysis - Allocated Cost Displays a bar graph of the historical spend analysis for the allocated resources with an actual and projected spend for the last three months.
Top Spend Displays the services and accounts that are consumed the most in your business unit or cost center. You can use the drop-down list in the right corner to select Top services or Top accounts .
Unallocated Cost Displays the list of unallocated resources along with the cloud type, associated accounts, or subscriptions. You can also view the total cost incurred for each resource.

You can also allocate unallocated resources to a cost center. For more information, see Allocating Unallocated Resources To Cost Center.

Allocated Cost Displays detailed information for the allocated resources that include the following.
  • Business unit or cost center
  • Owner of the business unit and cost center
  • Total cost of the allocated resources
  • Definition of the business unit or cost center. For example, a business unit constituted of four cost centers.

In the Actions column, you can click the Edit and Delete buttons to edit the resource details or delete the resource.

You can use the drop-down list in the top-right corner of the Allocated Cost table to filter the resources by business unit, cost center, or business unit and cost center.

You can also click the share and download icons in the top-right corner to share or download the resource details.

Chargeback View (Owners and Viewers)

The owners and viewers can view the business units and cost centers for which they have access.

You can use the View Selector (public cloud) and View Selector (Nutanix) to select the business unit or cost center.

Note: Owners and viewers have only view access to the business units and cost centers unless they are an administrator. Owners help in identifying the financial owner for the business unit or cost center.

The following table describes the widgets available for business unit and cost center views.

Table 2. Chargeback Views (Owners and Viewers)
View Description
Spend Overview Displays the total spend cost (month to date) and the projected spend cost for the business unit or cost center.
Spend Analysis - Allocated Cost Displays a bar graph of the historical spend analysis for the allocated resources with an actual and projected spend for the last three months.
Top Spend Displays the services and accounts that are consumed the most in your business unit or cost center. You can use the drop-down list in the right corner to select Top services or Top accounts .
Allocated Cost Displays detailed information for the allocated resources (within a cost center) that includes the following.
  • Cloud type ( Nutanix , AWS , Azure , or GCP )
  • Name of the account, subscription, or cluster
  • Account, subscription, or cluster ID
  • Total cost incurred for the account, subscription, or cluster.
You can use the expand icon to view details about services within the account or subscription.
Note: If the pulse was not available for a Nutanix cluster for a given number of days in a month, the Unmetered Cluster Cost line item appears showing the cluster cost incurred for those days. For more information, see Cost Analysis (Nutanix).

You can click View Details against each service to view the resource details.

You can also click the share and download icons in the top-right corner to share or download the detailed report for the cost center.

Budget

The Budget feature in Beam extends the budgeting capability for a business unit, cost center, or scope. A budget allows you to centralize the budget at the business unit, cost center, or scope levels to ensure that your consumption is within the budget that you have defined. You can also create custom budgets.

Beam monitors and tracks the consumption continuously, and you can track any threshold breaches to the budgets that you have configured using the Budget page in the Beam console. Organization level budgets can be tracked at the quarterly or yearly level basis for the selected business unit, cost center, or custom budgets.

The Budget page allows you to view the budget cards based on the budgets that you have configured for your cloud accounts.

The budget card for a business unit or cost center displays the Budgeted amount , Current Spend , and Estimated spend . You can also edit the budget details or delete an existing budget using the Budget page.

You can define and track a budget based on the following resource groups.

  • Business Unit/Cost Centre based Budget – You can select multiple business units and cost centers to create a resource group. You can only select the business units and cost centers for which you have access.
  • Scope based Budget - You can create only one budget for each scope.

You can add a threshold for your budget alerts. When the budget reaches the threshold you specified, Beam sends a notification to the email addresses you enter when creating the budget alerts.

Creating a Budget Goal

Beam allows you to create Budgets based on the resource groups that you have defined.

About this task

A budget allows you to centralize the budget at the business unit, cost center, or scope levels to ensure that your consumption is within the budget that you have defined.

To add a global Budget, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Budget .
  2. Click Create a Budget .
  3. In the Select Type page, select Custom Scopes based Budget or Business Unit/Cost Centre based Budget . Then click Next to go to the Define Resource Group page.
    Note: The custom budget option is not available for the Nutanix cloud. You can only create a business unit or cost center-based budget for the Nutanix cloud.
  4. Select the business units and cost centers or Scopes (if you selected Custom Scopes based budget ) from the resource drop-down menu to define the scope for the budget and click Next to go to the Allocate Budget page.
    Note: You can select the business unit and cost center from the drop-down menu only if you have access to the resource group item.
  5. In the Budget Name box, enter a budget name you want.
  6. In the Financial Year list, select the financial year session.
  7. In the Allocation Type area, select Automatic Allocation or Manual Allocation .
    Note: Selecting Automatic Allocation allows Beam to allocate budget based on your spend. Beam uses the last 40 days of data to project the budget for the current and next month.
  8. If you select Manual Allocation , do the following.
    1. In the Set Annual Budget field, enter the Annual Budget for the selected business center and cost center.
    2. To distribute the annual budget equally for all the quarters, click Distribute Equally .
      Alternatively, you can set the budget for each quarter manually. Similarly, you can either distribute the quarterly budget manually for each month or click Distribute Equally to distribute the quarterly budget equally for all the months. The monthly and quarterly budgets must add up to the annual budget that you have entered.
  9. Click Next .
    The Add Alerts to your Budget page appears.

    You can add percentages of the total budget value. When the budget reaches the threshold value you entered, Beam sends a notification via an email to the email addresses you enter.

    You can add alerts for the following periods.

    • Monthly Budget Alerts
    • Quarterly Budget Alerts
    • Yearly Budget Alerts
  10. Click Create against the period for which you want to create a budget alert.
    The Budget Alert page appears.
  11. In the Threshold box, enter the threshold value in percentage. Then click Save .
  12. In the Alert Notification box, enter the email addresses to which you want to send the alerts. Then click Save to create the budget.
    Note: Beam sends the budget alert notifications to the owners of the business unit, cost centers, or Scopes by default.

Budget Details

You can view your budget details from the Budget page in Beam. To view budget details, click View Details option in any of the budget cards. The Year Breakup and Cost Breakup for the budget is displayed.

To download or share the cost breakup report, click the download or share icon.

Expired Budgets

In the top-right corner, you can click the Expired button to view the expired budgets.

You can do the following in the expired budgets view.

  • Click the View Details option in any of the expired budget cards to view the details.
  • Click the Renew option to renew the latest expired budget for the current financial year.
    Note: The Renew option is available only for the latest expired budget. In case a budget for a resource group is already created for the current financial year, the renew option for the expired budget of the same resource group is not available.

Editing Budget Alerts

You can edit the budget alerts for the cost centers and business units in the Budget page. In the Budget page, you can view the budget cards for your cost centers and business units.

About this task

A budget allows you to centralize the budget at the business unit, cost center, or scope levels to ensure that your consumption is within the budget that you have defined.

To edit the budget alerts for your cost centers, business units, or scopes, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Budget to open the Budget page.
  2. Click Edit against the business unit, cost center, or scope to edit the budget alerts.
    The Edit the Budget page appears.
  3. Click Budget Alert tab.
    You can view the details of the alerts in the Categories area.
    You can view the following icons in the Action column.
    • Disable Alert or Enable Alert icon - Click to disable or enable the alert.
    • Edit Alert icon - Click to edit the alert.
    • Remove Alert icon - Click to remove the alert.
  4. Click the Edit Alert icon to edit the alert.
    The Budget Alert page appears.

    You can edit the period and threshold values.

  5. Click Save to save your changes.
  6. In the Alert Notifications box, enter the email addresses to which you want to send the alerts.
  7. Click Update to update the budget alert.

Scopes

A scope is a logical group of your cloud resources that provides you with a custom view of your cloud resources. You can define scopes using cloud, accounts, and tags. The administrator can assign read-only access to a user. The user gets read-only access for the resources within the scope and not the cloud accounts that constitute the scope. After you create a scope, click View in the top-right corner to open the User Interface Layout and select the scope.

Creating a Scope

A scope is a logical group of your cloud resources that provides you with a custom view of your cloud resources.

About this task

This section describes the procedure to create a scope.
Note: Only a Beam administrator can create a scope.
Note the following points when creating a scope for your Nutanix cloud resources.
  • The parent account is equivalent to the Nutanix account.
  • The child account is equivalent to a cluster.
  • The tags are equivalent to the category. For more information on Prism categories, see Category Management.

To create a scope, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Scopes .
  2. Click Create a Scope to open the Scope Creation page.
    In the Scope Creation page, you need to enter a scope name and add viewers from the list available. Then you need to define the scope based on cloud, account, and tags.
  3. In the Name box, enter a name for the scope.
  4. In the Viewers list, select the viewers for the scope you are creating.
  5. Click Define Scope to select the cloud, account, and tags.
  6. In the Define Scope page, do the following.
    1. In the Cloud list, select Nutanix .
    2. In the Parent Account list, select the parent account for which you want to create a scope.
    3. In the Sub Accounts list, select the sub accounts from the list available.
      The Sub Accounts list displays all the sub accounts within the parent account you selected.
    4. In the Tag Pair area, select the key and value pairs.
      You can click the plus icon to add multiple key and value pairs.
    5. Click Save Filter to save your filter.
      You can click Add Filter to create more filters.
    6. Click Save Resource Group to save your scope definition and close the Define Scope page.
  7. In the Scope Creation page, click Save Scope to create the scope.
    You can select and view the scope you just created using the User Interface Layout.

Licensing

This section provides information about the supported licenses for your Beam accounts, license entitlement for Nutanix on-premises, and subscription entitlement for public clouds.

The supported licenses are as follows. If you have any of the following licenses, you can convert your Beam account to a paid state.
  • NCM Ultimate
  • NCM Pro
  • Prism Ultimate
The Licensing page allows you to:
  • View information about license entitlement (required for accessing cost management features for Nutanix On-premises).
    • Status can be In Trial , License Applied , Trial Expired , or License Expired .
  • Activate your license ( Apply License or Validate License ) to convert from In Trial or Expired to the License Applied status.
  • View information about Beam public cloud subscription (required for accessing cost management features for Public Cloud).
    • Status can be In Trial , Subscription Active , Trial Expired , or Subscription Expired .
  • Purchase public cloud subscriptions using the Purchase Online Now option.
Note: Only the Beam account owner can view the details on the Licensing page.

To access the Licensing page, click Hamburger Icon > Configure > Licensing .

Figure. Licensing Page Click to enlarge

License Entitlement for Nutanix - Status

Refer to the following table to know about the various statuses available for your Beam account.

Status Description
In Trial A banner gets displayed notifying you about the trial period and suggesting you purchase a license.
Trial Expired or License Expired The Expired status appears after your trial period gets over or the applied license gets expired. You would not be able to use the Beam features and need to purchase the license.
License Applied Indicates that your license is applied. You can also view the expiry date for the license.

License Entitlement for Nutanix - Actions

The following two cases may occur after the license gets applied:

System detects a valid license
Beam checks if the supported license is available for the Beam account in which you are logged in.
  • If a license gets detected, the License is Found status gets displayed along with the Apply License option to apply for the license manually. After you perform this action, the status changes to License Applied along with the expiry date.
  • You need to perform the Apply License action only for the first time after you buy a license and log on to Beam. Beam periodically checks for any new licenses that you purchased, then applies the license or updates the expiry date accordingly.
    • Scenario 1: Beam detects L1 (expiry date as 31 December 2021) on 1 January 2021 and you click Apply License to activate the license. On 31 December 2021, Beam detects L2 (expiry date as 31 December 2022) and automatically applies the license.
    • Scenario 2: Suppose you buy multiple licenses with different expiry dates. For example, L1 and L2 with expiry dates as 21 June and 21 December. Beam will show the license with the farthest expiry date (21 December) once the data about the new purchases get discovered through periodic checks.
System does not find a valid license
Suppose you have any one of the supported license and Beam is unable to identify or recognize your license due to some reason and shows the License Not Found status. The Validate License option allows you to manually enter and validate your license key.
The validation may fail due to the following reasons:
  • You entered an invalid license key.
  • You entered a valid license key that belongs to another MyNutanix account. The reason for validation failure is that the Beam account can only be linked to a single MyNutanix account. Contact Nutanix support for further help.
.

Subscription Entitlement for Public Clouds - Status

For public clouds (AWS and Azure), one of the following statuses get displayed on the Licensing page:

Status Description
In Trial A banner gets displayed to notify you about the trial period and an option to purchase a subscription. To purchase a subscription, click Purchase Online Now , which redirects you to the Nutanix Billing Center.
Subscription Active This status indicates that you have an active subscription. The expiration date of the active subscription is also displayed.
Trial Expired or License Expired The Expired status appears after your trial period gets over or the active subscription gets expired. You would not be able to use the Beam features and need to purchase or renew the subscription.

Feature Violations

You must have a valid license and subscription to use the Beam features for your Nutanix on-premises and public clouds. If you do not purchase a license or subscription, a banner gets displayed at the top of the Beam page indicating that there are feature violations.

Feature violations occur in the following cases:
  • You have an active license but you are using the public cloud features in Beam without an active subscription.
  • You have active public cloud subscriptions but you are using the Nutanix features in Beam without a license.

Beam API

Beam provides API services to allow you to programmatically retrieve data from the Beam's platform and perform different configurations.

The following are a few scenarios for using the API services:
  • You can programmatically retrieve analyze data for your cloud accounts using API. You can select the resource group to raise a query. For example, you can raise a query for a business unit or a cost center. For more information, see the Analysis v2 or Analyze sections in the Beam API Reference Guide.
  • You can use APIs for remote onboarding of your cloud accounts without the need to log in to the Beam GUI. For more information, see dev.beam.nutanix.com.
  • You can perform CRUD operations on business units, cost centers, and scopes using APIs. For more information, see the Cost Governance - Multicloud section in the Beam API Reference Guide .

Cost Management for Public Cloud

Beam allows you to track your cloud expenses, optimize your cloud cost, and achieve visibility into your spend. Beam centralizes all your cloud expenses and multiple accounts into a single place and simplifies cloud cost management.

The supported public clouds are AWS , Azure , and GCP .

AWS

Support for AWS allows you to track your AWS cloud expenses, optimize your cloud cost, and achieve visibility into your spend. Beam centralizes all your AWS cloud expenses and multiple AWS accounts into a single place and simplifies cloud cost management.

For a consolidated billing, you must sign up in the AWS Billing and Cost Management console and designate your account as a payer account. You can link other accounts (linked accounts) to the payer account for consolidated billing. In AWS consolidated billing, the payer account is charged for all the linked accounts every month. For more information, see AWS Billing and Cost Management User Guide on AWS documentation website .

Beam helps you to optimize AWS services like EC2, RDS, EBS, EIP, Route53, Workspace, EC2, DynamoDB, ELB, Redshift, and ElastiCache.

Note: The historical spend reported in Beam is delayed by at least 48 hours. The cloud providers take around 24 to 48 hours to update the complete billing data.

Azure

Support for Azure enables you to take control of your cloud spend on the Azure cloud. Beam helps you to optimize the Azure services like Managed Disks, Azure SQL DB, VM, Public IP, PostgreSQL Server, MySQL Server, Load Balancer, Application Gateways, SQL DataWarehouse, and Redis Cache.

Beam now supports the following two Azure billing account types for cost governance.
  • Enterprise Agreement (EA)
  • Microsoft Customer Agreement (MCA)
Note: The historical spend reported in Beam is delayed by at least 48 hours. The cloud providers take around 24 to 48 hours to update the complete billing data.

Google Cloud Platform

Support for Google Cloud Platform (GCP) allows you to track your GCP resources and provide insights into your cost spends. Beam centralizes all your GCP cloud expenses and multiple GCP accounts into a single pane and simplifies cloud cost management.

Beam helps you analyze your GCP services like Compute Engine, Cloud Storage, Kubernetes Engine, and BigQuery.

Note: The historical spend reported in Beam is delayed by at least 48 hours. The cloud providers take around 24 to 48 hours to update the complete billing data.

Multicloud Views

Apart from providing cost visibility and optimization recommendations for individual clouds, Beam also provides cost visibility and optimization recommendations for entities with multiple clouds (Nutanix, AWS, Azure, and GCP). You can configure two types of multicloud entities - Financial and Scope.

Financial is a hierarchical structure comprising of Business units and Cost Centers used for Chargeback. Chargeback allows you to group cloud resources across multiple clouds (Nutanix, AWS, Azure, and GCP) within Cost Centers and Business units. By design, a cloud resource cannot be part of different cost centers or business units. For more information, see Chargeback.

Scope is a custom resource group with resources across multiple clouds (Nutanix, AWS, Azure, and GCP). Scopes are useful in providing visibility to logical resource groups like applications, project teams, cross-functional initiatives, and more. Hence, by design, a cloud resource can be part of multiple Scopes. For more information, see Scopes.

User Interface Layout

This section provides information on the layout and navigation of the Beam console.

The Beam console provides a graphical user interface to manage Beam settings and features.

View Selector

When you log on to the Beam for the first time, the View Selector pop-up appears. The View Selector pop-up allows you to search for an account by typing the account name in the search box or navigate and select a cloud account, business unit or cost center, and custom scope.

The Dashboard is the welcome page that appears after logging and selecting a view in Beam.

Figure. View Selector Click to enlarge

For the subsequent logins, the last visited page for the last selected view (account, business unit or cost center, and scope) appears. You can click View in the top-right corner to open the View Selector pop-up and select a different view.

Table 1. Available Views
View Description
All Clouds Select this view to get total cost visibility for AWS-, Azure-, GCP-, and Nutanix-accounts for which you have access.
Cloud Accounts (AWS, Azure, GCP, and Nutanix) Allows you to select AWS, Azure, GCP, and Nutanix accounts.
Financial Allows you to select business units or cost centers you created for the chargeback.
Scopes Allows you to select the custom scopes you created.

Beam Console

The Beam Console screens are divided into different sections, as described in the following image and table.

Figure. Beam Console Overview Click to enlarge

Table 2. Beam Console Layout
Menu Description
Hamburger icon Displays a menu of features on the left. When the main menu is displayed, the hamburger icon changes to an X button. Click the X button to hide the menu.
Alerts The Alert option allows you to see system-generated alert notifications. Click the bell icon from the main menu bar to view alerts. Click See More to view the complete list of notification.
User Menu The user drop-down menu has the following options.
  • Profile - Displays your account information, timezone and email preferences, and Product Access (read/write) for Beam.
  • What's New - Displays the recent product updates.
  • Terms of Service
  • Privacy Policy
  • Responsible Disclosure
  • Log out - Click to log out of the Beam console.
Help Menu You can click the question mark icon in the top-right corner of the console to view the following:
  • Read Documentation - Redirects you to the Beam documentation.
  • Guided Tours - Opens the list of walkthrough videos that helps you to navigate through various tasks and workflows in Beam.
Widgets Section The widgets section displays the informational and actionable widgets corresponding to the feature that you have selected from the main menu. For instance, the Dashboard page display widgets like Spend Overview , Spend Analysis , Save , and Cloud Efficiency .
View option Click View in the top-right corner to open the View Selector pop-up.

Main Menu

Clicking the Hamburger icon displays a menu of features on the left. When the main menu is displayed, the Hamburger icon changes to an X button. Click the X button to hide the menu.

Figure. Main Menu Click to enlarge

The following table describes each feature in the main menu.

Table 3. Main Menu - Available Features
Feature Description
Dashboard Displays the Dashboard page (see Dashboard).
Analyze Displays the Analyze page (see Analyze - Cost Analysis).

Analyze allows you to track cost consumption across all your cloud resources at both the aggregate and granular level. You can drill down cost further based on your services, accounts, or application workload.

Chargeback Displays the Chargeback page (see Chargeback).

Enables the financial control of your cloud spends by providing the ability to allocate cloud resources to departments based on definitions. It provides a consolidated view across all your cloud accounts in a single pane for Finance views.

Budget Displays the Budget page (see Budget).

A budget allows you to centralize the budget at the business unit, cost center, or scope levels to ensure that your consumption is within the budget that you have defined.

Reports Displays the Reports page (see Cost Reports).

Beam generates reports to track cost consumption across all your cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications. The reports are generated automatically and are available to view, download, or share from the Beam console.

Save Displays the Save page (see Save - Cost Saving).

Helps you save money on cloud spend by identifying unused and underutilized resources. Also, you get specific recommendations for optimal consumption.

Purchase Displays the Purchase page (see Purchase - Recommendations).

Provides insights on overall RI usage statistics, recommended RI purchases, managing existing RI portfolio, and RI coverage.

Playbooks Displays the Playbooks page (see Playbooks).

Allows you to automate actions on your public cloud environment for better cloud management. It helps you to improve your operational efficiency by reducing manual intervention.

Configure menu The Configure menu allows you to do the following operations.
  • Add and manage cloud accounts in Beam.
  • Manage Beam users
  • Integrate third-party applications
    • Slack
    • ServiceNow Integration with Nutanix Beam
  • Cost Policy
  • Chargeback
  • Scopes
  • AWS Cost Configuration
  • Budget Alerts
  • AWS Invoice

Administration and User Management

Beam allows you to do the following administrative controls.

  • Add and manage users accessibility to various cloud accounts in Beam.
  • Two types of access can be granted to a user.
    • Admin Access - The user gets read and write access to all cloud accounts added in your Beam account.
    • User Access - The administrator can grant Read Only or Read & Write permissions on selected cloud accounts to a user, thus allowing the administrator to exercise the principle of least privilege.

Adding a Beam User

You can add and manage users using the Beam console.

About this task

To add a user in Beam, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > User Management . Click Add User .
  2. In the Details page, enter the user details and change the timezone as desired. Then, click Next to go to the Permissions page.
    In the Permissions page, you can choose Admin Access or User Access .
  3. Click Admin Access if you want to give administrator rights to the user. See User Roles for details on types of users. Then, click Save to complete the task.
  4. Click User Access if you want to grant Read Only or Read & Write permissions on selected cloud accounts to the user.
    1. Select the required access ( No Access , Read Only , and Read & Write ) across clouds.
      The No Access option is selected by default.
    2. Select the AWS Payer Account and Linked Accounts, Azure Billing Accounts and Subscriptions, Nutanix accounts, and GCP Billing Accounts and Projects for which you want to provide access. Then, click Save to complete the task.
    Figure. User Management - Granting Permissions Click to enlarge

User Roles

This section helps you to understand all the different roles in Beam and when you would use each.

Figure. Beam User Roles Click to enlarge User Roles
Owner Role

When a user creates a Beam subscription, a tenant is triggered and the user becomes the owner of that tenant.
 An owner is shown as Admin (Owner) in the User Management page. The owner role has the following attributes.

  • Create other users with or without administrative privileges.
  • Access billing subscription information.
  • Access to licensing information. For more information on licensing for AWS, Azure, and GCP accounts, see Licensing.
  • Access to all features.
  • View the admin menu.
  • Perform all the read or write operations.
  • Create or edit budgets.
  • View, create, edit, or delete cost centers.
  • Restrict access to a limited number of cloud account for a user.
Note:
  • My Nutanix Account Administrators are considered as Owner in Beam.

    You can't create an owner role in Beam. However, you can create as many as three Beam owners from My Nutanix. Only My Nutanix Account Administrators have the necessary permissions to create Beam owners. For more information on My Nutanix user management, see Cloud Services Administration Guide .

  • Only My Nutanix Account Administrators or Beam Owners are able to manage billing and renewals of Beam subscription. For more information on managing billing and renewals, see Cloud Services Administration Guide.
Administrator Role

An administrator is shown as Admin in the User Management page. The administrator role has the following attributes.

  • Access to all features.
  • View the admin menu.
  • Add other users.
  • Perform all the read or write operations.
  • Create or edit budgets.
  • View, create, edit, or delete cost centers.
  • Restrict access to a limited number of cloud account for a user.
User Role

A user role is created by granting read-only or read & write permission for selected accounts.

  • An account having a user role cannot create other users.
  • An account having a user role with read-only permission can view the cost data.
  • Read-only or read & write permission can be granted on the selected Nutanix accounts.

ADFS Integration

Active Directory Federation Services (ADFS) is a Single Sign-On (SSO) solution that you can use for implementing single sign-on in Beam. To integrate ADFS with Beam, log on to your MyNutanix account, and perform the integration. See SAML Authentication for details. To log on to your Beam account using ADFS, see Logging into Xi Cloud Services as an SAML User .

User Management

You can configure the following user group types in ADFS.
  • Administrator user - Users added to this group have administrator access.
  • Beam user - Users added to this group can perform operations based on the access policy assigned by the administrator user.
Note:
  • If you are a part of the Beam user group and logging into Beam through ADFS for the first time, you will not have access to any cloud account. Contact your account administrator to get access to an account.
  • If you are a part of the administrator user group and logging into Beam through ADFS, you cannot add and delete users using the Beam user management. You can perform these actions in ADFS.
  • If you are logging into Beam through ADFS, you cannot change roles (administrator to user or user to administrator). You can perform these actions in ADFS.

Support

If you log on to Beam through ADFS, you can get access to Nutanix Support only if your MyNutanix account was used to add your Beam user account. However, if your Beam user account was not added using your MyNutanix account, you do not get access to support.

Starting Beam Free Trial

Beam is a multi-cloud cost governance SaaS product that provides a free, full-featured, 14-day trial period. During the free trial period, you can configure your Nutanix On-premises and public cloud accounts (AWS, Azure, and GCP) in Beam to evaluate the features. It takes about 15 minutes to configure your cloud accounts in Beam.

About this task

The following section describes the procedure to start a free trial.
  • If you have access to the MyNutanix account, perform Step 1 .
  • If you do not have access to the MyNutanix account, perform Step 2 .

Procedure

  1. If you have access to the MyNutanix account, do the following.
    1. Login to your MyNutanix account.
    2. In the Dashboard, scroll down to find the Beam application. Then, click Launch to open the Beam application and start your free trial.
      Figure. MyNutanix Dashboard - Launching Xi-Beam Click to enlarge
  2. If you do not have an existing MyNutanix account, do the following.
    1. Open the Beam webpage.
    2. Click Start Free Trial and fill the form that appears. Then, click Submit .
      Figure. Free Trial - Form Click to enlarge
      Your MyNutanix account gets created. Also, you will receive a verification email that contains a link for logging into the Beam application.

What to do next

You can add your Nutanix, AWS, Azure, and GCP accounts in Beam.

Cloud Account Configuration (Onboarding)

The following sections describe the onboarding steps for AWS-, Azure-, and GCP-accounts.

Prerequisites - AWS, Azure, and GCP

Refer to this section to know about the access and permissions required to configure your cloud accounts in Beam.

AWS Account Onboarding Requirements

Ensure that you have the following access before starting with the account onboarding steps:
  • AWS access: Account Owner or administrator access to the AWS payer account.
  • AWS access: IAM user with access to AWS S3, AWS CloudFormation Template, AWS Billing & Cost Management console, and permission to create a role.
  • Beam administrator access.

Azure Accounts Onboarding Requirements

Enterprise Agreement
Ensure that you have the following access before starting with the EA billing account onboarding steps:
  • Enrollment administrator access.
  • (Optional) To verify if you have Enterprise Administrator access, go to https://jwt.io/. The configuration works if the token you tested has Enterprise or Indirect Enterprise listed.
    {
      "EnrollmentNumber": "XXXXXXXX",
      "Id": "027d019e-5674-4771-a09d-1XXXXXXX840",
      "ReportView": "Enterprise", (or Indirect Enterprise)
      "PartnerId": "",
      "DepartmentId": "",
      "AccountId": "",
      "iss": "ea.microsoftazure.com",
      "aud": "client.ea.microsoftazure.com",
      "exp": 1554264804,
      "nbf": 1538540004
    }
    
  • Beam administrator access.
Note:
  • Only Enrollment Access Keys are accepted in Beam.
  • Access key activation may take up to 30 minutes.
Microsoft Customer Agreement
Ensure that you have the following access before starting with the MCA billing account onboarding steps:
  • You must have a Billing Account Owner role for adding an MCA billing account.
  • You must provide Billing account reader access to the application.
  • Beam administrator access.

GCP Account Onboarding Requirements

Ensure that you have the following access before starting with the account onboarding steps:

  • Permissions and Roles: Beam requires access to specific APIs and a service account. A GCP service account is an authorized identity to enable authentication between Beam and GCP. A set of predefined and primitive roles grant the service account the permissions it requires to complete specific actions on the resources in your GCP project/billing account or organization. For more information, see IAM Roles and Required Permissions.
    Note: Your GCP projects does not have to be a part of an organization in order for Beam to fetch the billing data.
  • Beam administrator access.

GCP Onboarding - Overview

To enable Beam to retrieve data on your Google Cloud Platform (GCP) resources and provide insights into your cost spend, you must onboard your GCP billing accounts to Beam. You can add multiple GCP billing accounts in Beam and get an insight into your cost spend.

Terminology Reference

The following table introduces the principal GCP terms and entities:

Table 1. Terminology Reference
Term Description
Project A project organizes all your Google Cloud resources. A project consists of a set of users; a set of APIs; and billing, authentication, and monitoring settings for those APIs. For example, all of your Cloud Storage buckets and objects, along with user permissions for accessing them, reside in a project. You can create single or multiple projects and use them to organize your Google Cloud resources, including your Cloud Storage data, into logical groups.
Billing Account

A cloud-level resource managed in the GCP console.

It tracks all of the costs (charges and usage credits) incurred by your Google Cloud usage. You can link one or more projects to a billing account. Project usage gets charged to the linked Cloud Billing account.

For more information, see the Overview of Cloud Billing Concepts section in the Google Cloud Documentation .
BigQuery Table

Contains individual records organized in rows. Every table is defined by a schema that describes the column names, data types, and other information.

You must provision the Big query table in one of the projects. The table will store the billing data for all the projects within the billing account. Beam pulls the billing data from the BigQuery table and provides insight into your GCP cloud spend.

Service Account A special kind of account used by an application (not a person) to make authorized API calls.
  • Beam creates a Service account on-the-fly while performing the onboarding steps for the first GCP billing account. For the subsequent billing accounts, Beam will auto-populate the previously created service account information on the onboarding page.
  • You need to provide certain permissions to the Service account so that Beam can pull the billing data and provide cost insights. To achieve this, you need to create a few IAM roles in the GCP console and attach them to the Service account. For more information, see IAM Roles for GCP Billing Exports.

Getting Started With Onboarding

Perform the following steps to onboard your first GCP billing account in Beam:
  1. Create a Service account from the Beam console

    The Service account for your enterprise gets created in Nutanix's own secure GCP Project. You need to create IAM roles with the required permissions and attach them to the Service account so that Beam can fetch the billing data and provide cost insights.

  2. Create a BigQuery dataset if not already created (GCP Console). Then perform the Export cloud billing data to BigQuery operation.
  3. Create and attach IAM Roles and Required Permissions for users with and without access to GCP organizations.
  4. Enter the GCP billing account details in the Beam console to complete the onboarding process.
Warning: If you have access to a billing project with no access to its billing account, you cannot onboard such billing accounts in Beam.

Adding GCP Billing Account

This section describes the procedure to add your first GCP billing account in Beam. Beam fetches the billing data of all projects associated with the given billing account and provides visibility into your spend.

About this task

Warning: If you have access to a billing project with no access to its billing account, you cannot onboard such billing accounts in Beam.

To add a GCP billing account in Beam, do the following:

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > GCP Accounts .
  2. Click Add a GCP Billing Account .
    The GCP Account Onboarding page appears.

    If you are onboarding your first billing account, an option to create a service account is visible. For the subsequent billing accounts, Beam auto-populates the previously created service account ID on the Configure Permissions page.

  3. Click Create a Service Account .
    Beam creates a service account on-the-fly. The service account for your enterprise gets created in Nutanix's own secure GCP Project. Provide the required permissions to this account so that Beam can retrieve the billing data and provide cost insights.
    Note: The Service account created when onboarding the first GCP billing account gets used for the subsequent GCP billing accounts. When onboarding the subsequent GCP billing accounts, the service account field gets auto-populated in the Configure Permissions page.
    Figure. GCP - Service Account Details Click to enlarge
  4. Before you start adding the billing source information in the Input Billing Source page, do the following:
    1. Create a BigQuery dataset if not previously created (GCP Console). Then perform the Export cloud billing data to BigQuery operation.
      Note: Beam only supports Standard Usage Cost Data option.
    2. Create the required IAM roles and attach them to the service account in the GCP Console. For more information, see IAM Roles and Required Permissions.
    After you have created the IAM roles and attached them to the Service account, go to the Configure Permissions page in the Beam console and click Next .
    Figure. GCP Onboarding - Adding Billing Account Details Click to enlarge
  5. Enter the Billing Account Name , Billing Account ID , Project ID , and Dataset ID .
    Ensure to fetch the correct billing account details from the GCP console. For more information, see Fetching the Billing Account Details .
  6. When all the field entries are correct, click Validation and Save to complete the onboarding process.
    Your first GCP billing account is successfully configured in Beam.
Adding Multiple GCP Billing Accounts

About this task

The service account created when onboarding the first GCP billing account is used for the subsequent GCP billing accounts. The service account field is auto-populated when onboarding the next GCP billing accounts in Beam.

Perform the following steps to onboard your subsequent GCP billing accounts in Beam:

Procedure

  1. Create and attach the following IAM roles to the service account in the GCP Console:
    • beam-bill-ingestion-role (Mandatory) : Attach this role to the billing project in which the BigQuery Table is provisioned or the billing account according to your business requirements. You do not need to create this role again as you previously created this role at the organization level when onboarding your first GCP billing account.
    • beam-project-metadata-role (Optional) : Creating and attaching this IAM role is optional. You do not need to create and attach this role to the service account for the subsequent GCP billing accounts if you previously performed these steps when onboarding your first GCP billing account.This role is created and attached at the organization or folder level. Hence, it applies to all billing accounts within the organization or folder.
  2. Enter the GCP billing account details in the Beam console to complete the onboarding process.

IAM Roles and Required Permissions

You can follow one of the given options to provide the required IAM roles and permissions:

  • Users with access to GCP Organizations
  • Users without access to GCP Organizations
Users with access to GCP Organizations

Beam needs certain permissions to fetch the billing data and provide cost insights. For users with access to GCP organizations, you need to create two IAM roles and attach them to the service account created by Beam. Refer to this section to get an understanding about the IAM roles and its required permissions.

The required IAM roles are as follows:
(Mandatory) beam-bill-ingestion-role
Allows Beam to ingest bills from the BigQuery table and read Projects associated with a given billing account.
Role Created At Role Attached At Role JSON (Use JSON to programmatically create the role)
Organization level Billing project level and Billing account level
{
    "description": "Allows Beam to ingest bills from BigQuery and read Projects associated with a given billing account",
    "includedPermissions": [
"resourcemanager.projects.get",
      "bigquery.datasets.get",
      "bigquery.jobs.create",
      "bigquery.tables.get",
      "bigquery.tables.getData",
     "bigquery.readsessions.create",
     "bigquery.readsessions.getData",
   billing.resourceAssociations.list],
    "name": "beam-bill-ingestion-role-v1",
    "stage": "GA",
    "title": "Nutanix Beam Bill Ingestion Role (v1)"
}
(Optional) beam-project-metadata-role
Allows Beam to read project names, folder hierarchy, and folder names.
This role enables Beam to get the details of a project. For example, the billing account to which the project is associated, the name of the project, and so on. If you do not provide this permission, Beam will only show the Project ID in its console.
Note: Provide this permission for a specific project or the parent folder if you want to view the labels of the projects in Beam.
Role Created At Role Attached At Role JSON (Use JSON to programmatically create the role)
Organization level Folder or organization level
{
  	"title": "Nutanix Beam Project and Folders metadata read",
    "name": "beam-project-metadata-role",
    "description": "Allows Beam to read Project names, Folder hierarchy and Folder name",
    "includedPermissions": [
      "resourcemanager.projects.get",
      "resourcemanager.folders.get"
    ],
    "stage": "GA"
}
Note: The IAM role name provided in this topic is a recommendation. You can use a different role name if you want.

To create the roles in the GCP Console, see Creating IAM Roles.

GCP Permissions Required to Create and Attach IAM Roles

Refer to the following table to understand the GCP permissions to create and attach the IAM roles required by Beam.

Task GCP Role
Create and attach roles at Organization level
  • Organization Role Administrator role (roles/iam.organizationRoleAdmin) : GCP inbuilt role to create roles at the organization level.

    This role provides access to administer all custom roles in the organization and its associated projects.

  • resourcemanager.organizations.setIamPolicy : Additional permission required to attach roles.
Create and attach roles at Project level
  • Role Administrator role (roles/iam.roleAdmin) : GCP inbuilt role to create roles at the project level.

    This role provides access to all custom roles in the project.

  • resourcemanager.projects.setIamPolicy : Additional permission required to attach roles.
Create and attach roles at Folder level
  • Folder Admin (roles/resourcemanager.folderAdmin) : GCP inbuilt role to create roles at the folder level.

    This role provides all available permissions for working with folders.

  • resourcemanager.folders.setIamPolicy : Additional permission required to attach roles.
Attach roles at Billing account level roles/billing.admin : GCP Inbuilt Role to attach roles at the Billing account level.
Creating IAM Roles

This section describes the procedure to create the required IAM roles in the GCP console for the user with access to GCP organizations.

Before you begin

  • Refer to Users with access to GCP Organizations to get an understanding about the IAM roles and its required permissions.
  • You require specific GCP permissions to create and attach the IAM roles required by Beam. For more information, see the GCP Permissions Required to Create and Attach IAM Roles section in Users with access to GCP Organizations.

About this task

To create the required IAM role, do the following:

Procedure

  1. In the GCP Console, go to the Roles page.
  2. In the drop-down menu at the top of the page, select the organization in which you want to create the IAM roles.
    IAM Role Entity
    (Mandatory) beam-bill-ingestion-role Organization level. For example, nixbeam.com .
    (Optional) beam-project-metadata-role Organization level. For example, nixbeam.com .
    Note: The IAM role name provided in the table is a recommendation. You can use a different role name if you want.
  3. Click Create Role .
  4. In the Create Role page, enter the following information:
    Option Description
    Title

    Enter the role name you are creating.

    Role name: beam-bill-ingestion-role or beam-project-metadata-role .
    Description

    Enter a description for the role.

    Example: Allows Beam to ingest bills from the BigQuery table and read Projects associated with a given billing account for beam-bill-ingestion-role .
    ID Enter the role ID in the following format: beam_bill_ingestion_role or beam_project_metadata_role .
    Role launch stage Select General Availability .
  5. Click ADD PERMISSIONS .

    The Add Permissions window appears.

  6. In the Filter table search box, search for the permission and then select the checkbox.

    Refer to Users with access to GCP Organizations to view the required permissions for the role that you are creating.

    Repeat this step to search and select the remaining permissions.

    Figure. GCP IAM Role - Adding Permissions Click to enlarge
  7. Click ADD after you select all the required permissions.
    The added permissions appear in the assigned permissions area.
  8. Click CREATE to complete.

What to do next

Attach the IAM roles to the Service account.
Attaching IAM Roles to the Service Account

This section describes the procedure to attach the two IAM roles you created to the service account, for the user with access to GCP organizations.

Before you begin

You require specific GCP permissions to attach the IAM roles to the service account. For more information, see the GCP Permissions Required to Create and Attach IAM Roles section in Users with access to GCP Organizations.

About this task

To attach the IAM roles to the service account, do the following:

Procedure

  1. To attach beam-bill-ingestion-role to the service account, do the following:
    Note: This role is attached to the billing project in which the BigQuery Table is provisioned and to the billing account.
    1. To attach this role to the billing project, do the following:
      1. In the GCP Console, go to the IAM page.
      2. In the drop-down menu at the top of the page, select the project where you have provisioned the BigQuery Table.
      3. Click ADD at the top of the page. Then, go to Step 1.c.
        Figure. Billing Project - Adding Members Click to enlarge
    2. To attach this role to the billing account, do the following:
      1. In the GCP Console, go to the Billing page.

        A list of billing accounts appear.

      2. Click on your billing account.
      3. In the left pane, click Account management .
      4. Click ADD MEMBER . Then, go to Step 1.c.
        Figure. Billing Account - Adding Members Click to enlarge
    3. In the New members box, enter your service account name.
      You can also locate the service account name from Beam GCP account configuration console.
    4. In the Select a role list, search and select beam-bill-ingestion-role .
    5. Click SAVE to complete.
  2. (Optional) To attach beam-project-metadata-role to the Service account, do the following:
    Note: You can attach this role to the folder or organization according to your business requirements.
    1. In the GCP Console, go to the IAM page.
    2. In the drop-down menu at the top of the page, select the organization. For example, nixbeam.com.
    3. Click ADD at the top of the page.
      Figure. Organization - Adding Members Click to enlarge
    4. In the New members box, enter your service account name.
      You can also locate the service account name from Beam GCP account configuration console.
    5. In the Select a role list, search and select beam-project-metadata-role .
    6. Click SAVE to complete.
Users without access to GCP Organizations

Beam needs certain permissions to fetch the billing data and provide cost insights. For the users without access to GCP organizations, you need to create an IAM role and use a GCP inbuilt role and attach them to the service account created by Beam. Refer to this section to get an understanding about the IAM roles and its required permissions.

Note:
  • You need permissions to attach the roles at the billing account level.
  • Ensure that you create and attach the role only in the project that contains Billing export BigQuery Dataset.
The required IAM roles are as follows:
(Mandatory) beam-bill-ingestion-role
Allows Beam to ingest bills from the BigQuery table.
Role Created At Role Attached At Role JSON (Use JSON to programmatically create the role)
Project level Project level
{
    "description": "Allows Beam to ingest bills from BigQuery",
    "includedPermissions": [
      "bigquery.datasets.get",
      "bigquery.jobs.create",
      "bigquery.tables.get",
      "bigquery.tables.getData",
     "bigquery.readsessions.create",
     "bigquery.readsessions.getData"],
    "name": "beam-bill-ingestion-role-v1",
    "stage": "GA",
    "title": "Nutanix Beam Bill Ingestion Role (v1)"
}
Note: The IAM role name provided in this topic is a recommendation. You can use a different role name if you want.
(Mandatory) Billing Account Viewer
The Billing Account Viewer is a GCP in-built role and you need to attach that at the billing account level. Allows Beam to read Projects associated with a billing account, but does not confer the right to link or unlink projects or otherwise manage the properties of the billing account or the ability to read payments related information.
For more details on how to attach the Billing Account Viewer role, see Attaching IAM Roles to the Service Account.

To create the roles in the GCP Console, see Creating IAM Roles.

GCP Permissions Required to Create and Attach IAM Roles

Refer to the following table to understand the GCP permissions to create and attach the IAM roles required by Beam.

Task GCP Role
Create and attach roles at Project level
  • Role Administrator role (roles/iam.roleAdmin) : GCP inbuilt role to create roles at the project level.

    This role provides access to all custom roles in the project.

  • resourcemanager.projects.setIamPolicy : Additional permission required to attach roles.
Attach roles at Billing account level roles/billing.admin : GCP Inbuilt Role to attach roles at the Billing account level.
Creating IAM Roles

This section describes the procedure to create the required IAM role in the GCP console for the user without access to GCP organizations.

Before you begin

  • Refer to Users without access to GCP Organizations to get an understanding about the IAM roles and its required permissions.
  • You require specific GCP permissions to create and attach the IAM roles required by Beam. For more information, see the GCP Permissions Required to Create and Attach IAM Roles section in Users without access to GCP Organizations.

About this task

To create the required IAM role, do the following:

Procedure

  1. In the GCP Console, go to the Roles page.
  2. In the drop-down menu at the top of the page, select the project in which you want to create the IAM roles.
    IAM Role Entity
    (Mandatory) beam-bill-ingestion-role Project level
    Note:
    • The IAM role name provided in the table is a recommendation. You can use a different role name if you want.
  3. Click Create Role .
  4. In the Create Role page, enter the following information:
    Option Description
    Title

    Enter the role name you are creating.

    Role name: beam-bill-ingestion-role .
    Description

    Enter a description for the role.

    Example: Allows Beam to ingest bills from the BigQuery table .
    ID Enter the role ID in the following format: beam_bill_ingestion_role .
    Role launch stage Select General Availability .
  5. Click ADD PERMISSIONS .

    The Add Permissions window appears.

  6. In the Filter table search box, search for the permission and then select the checkbox.

    Refer to Users without access to GCP Organizations to view the required permissions for the role that you are creating.

    Repeat this step to search and select the remaining permissions.

    Figure. GCP IAM Role - Adding Permissions Click to enlarge
  7. Click ADD after you select all the required permissions.
    The added permissions appear in the assigned permissions area.
  8. Click CREATE to complete.

What to do next

Attach the IAM roles to the Service account.
Attaching IAM Roles to the Service Account

This section describes the procedure to attach the two IAM roles to the service account, for the user without access to GCP organizations.

Before you begin

You require specific GCP permissions to attach the IAM roles to the service account. For more information, see the GCP Permissions Required to Create and Attach IAM Roles section in Users without access to GCP Organizations.

About this task

To attach the IAM roles to the service account, do the following:

Procedure

  1. To attach beam-bill-ingestion-role to the service account, do the following:
    Note: This role is attached to the billing project in which the BigQuery Table is provisioned.
    1. In the GCP Console, go to the IAM page.
    2. In the drop-down menu at the top of the page, select the project where you have provisioned the BigQuery Table.
    3. Click ADD at the top of the page.
      Figure. Billing Project - Adding Members Click to enlarge
    4. In the New members box, enter your service account name.
      You can also locate the service account name from Beam GCP account configuration console.
    5. In the Select a role list, search and select beam-bill-ingestion-role .
    6. Click SAVE to complete.
  2. To attach Billing Account Viewer role to the service account, do the following:
    Note: This role has to be attached at the billing account level.
    1. In the GCP Console, go to the Billing page.
      A list of billing accounts appear.
    2. Click on your billing account.
    3. In the left pane, navigate to Account management .
    4. Click SHOW INFO PANEL at the top-right corner of the page.
    5. Click the ADD PRINCIPAL button.
      Figure. Billing Account - Adding Principals Click to enlarge
    6. In the New Principals box, enter your billing account name.
      You can also locate the service account name from Beam GCP account configuration console.
      Figure. Billing Account - Attaching Role Click to enlarge
    7. From the Role drop-down list, search and select Billing Account Viewer.
    8. Click SAVE to complete.
    Note: Beam does not have the ability to read name associated with the Projects and, it shows a soft warning on the GCP accounts configuration page.

Fetching the Billing Account Details

This section describes the procedure to fetch the billing account details ( Billing Account ID , Project ID , and Dataset ID ) that you need to add in the Beam console to complete the onboarding process.

About this task

To fetch the billing account details, do the following:

Procedure

  1. To fetch the Billing Account ID , do the following:
    1. In the GCP Console, go to the Billing page.
      A list of billing accounts appear.
    2. Click on the Billing account that you are onboarding in Beam.
    3. In the left pane, click Account management .

      You can view the Billing account ID at the top of the page.

      Figure. GCP Console - Billing Account ID Click to enlarge
  2. To fetch the Project ID and Dataset ID , do the following:
    1. In the Billing Account page, in the left pane, click Billing export .
    2. In the Billing export page, enable Standard usage cost and then, locate the Project name and Dataset name IDs.
      Note: Beam does not support Detailed usage cost table.
      Figure. GCP Console - Project and Dataset IDs Click to enlarge

GCP Billing Accounts - Management

Refer to this section to understand the actions you can take on the GCP billing accounts in Beam.

You can do the following:
  • View the list of projects linked to the billing account in the Projects tab.
  • View the billing project (project where your cloud billing data gets exported) in the Billing Sources tab.
  • Add a billing source: If you change the billing project in the GCP Console, you must add the new billing project in the Billing Sources tab.
  • Delete a billing account: Beam provides you an option to delete a billing account. Billing data and the related analytics information gets removed from Beam.

Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > GCP Accounts . Then, click Manage Account against the Billing account that you want to manage.

Figure. Beam Console - Managing Billing Accounts Click to enlarge
Adding a Billing Source

When you change the source of your BigQuery export in the Billing Account > Billing export (GCP Console) according to your business requirements, you must add the new billing source in the Beam console.

About this task

To add a billing source in the Beam console, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > GCP Accounts .
  2. Click Manage Account against the Billing account in which you want to add a billing source.
  3. Click the Billing Sources tab.
    Figure. Billing Sources Click to enlarge
  4. In the top-right corner of the page, click the Actions drop-down list. Then, click Add Billing Source .

    The Add Billing Source pop-up appears.

    Figure. Add Billing Source Click to enlarge
  5. Enter the Project ID and Dataset ID to start fetching the billing data for the new billing source.

    For more information on how to get the Project ID and Dataset ID, see Fetching the Billing Account Details .

  6. When all the field entries are correct, click Validate and Save to complete adding billing source.
    Note:
    • Suppose you change the projects to export your billing data for each month. Beam fetches the billing data from the previous billing projects and switches to the new billing project that you added.
    • You cannot delete the previous billing projects. Beam needs the historical billing data to provide cost insights accurately.
    • Only one project can be active at a given time. In the Billing Sources tab, in the Last Data Point column, you can view the current billing project (project with the latest date) along with the previous billing projects.
Deleting a Billing Account

Refer to this section to delete a Billing account from Beam.

About this task

To delete a Billing account in Beam, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > GCP Accounts .
  2. Click Manage Account against the Billing account that you want to delete.
  3. In the top-right corner of the page, click the Actions drop-down list. Then, click Delete Billing Account .

    The Deleting GCP Billing Account window appears.

  4. Enter the Billing Account ID and click Delete .
    Warning: You cannot undo the delete action. The Billing account and all the associated projects for all users in Beam gets deleted. Also, the historical spend data and historical reports for the Billing account get erased.

Adding AWS Account

This section describes the procedure to add your AWS payer account in Beam.

About this task

Adding an AWS account in Beam involves three steps:

To add an AWS Payer account, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > AWS Accounts .
  2. Click Add Payer Account .
  3. In the Account Configuration page, perform the following steps.
    1. In the AWS Account Name box, enter a name for your AWS account.
    2. In the AWS Account ID box, enter your AWS account ID.
      Click AWS Management Console (Support Center) to view your AWS Account ID.
    3. If you already have a CUR, do the following.

      1. In Report Name , enter the name for the CUR.

      2. In S3 Bucket Name , enter the name of your CUR bucket.

      3. In Report Prefix , enter the prefix of the CUR in AWS.

      You can click the Where can I find this? hyperlink to go to the AWS Cost and Usage Reports page in the AWS console. For detailed instructions on getting the report name, S3 bucket name, and report prefix of your existing CUR, see Getting Cost and Usage Report (CUR) Details (AWS Console).

      To get the report prefix path for your CUR, see Getting Report Path Prefix (AWS Console).

      If you do not have a CUR, create a CUR and enter the information in the Report Name , S3 Bucket Name , and Report Prefix fields. To create a CUR, see Creating Cost and Usage Report (AWS Console).
      Figure. AWS Payer Account Onboarding - Account Configuration Click to enlarge

    4. Select the access type you want to grant to Beam.
      The available options are as follows.
      • Spend Analysis and Optimize Recommendations : This option is selected by default. You cannot clear this option. Beam requires read permissions for spend analysis and optimize recommendations.
      • Click to Fix and Playbooks : Selecting this access type would allow you to act on the saving insights, optimize the costs from the Beam console, create and invoke the Lambda function for Playbooks, and perform Eliminate actions.

      For more information, see Required Permissions.

      Optionally, check to enable Enable one-click policy updates to support upcoming features. This option allows Beam to prepare the permission policy in case additional permissions are required for a feature. Once you select this option, you must update the policy for the account from the AWS Accounts page.
      Note: Beam adds audits to the savings policy frequently. You can take advantage of the new audits added by enabling one-click policy updates option for AWS.
    5. Click Next to go to the Review Configuration page.
  4. In the Review Configuration page, perform the following steps.
    1. Review the information you entered in the Account Configuration page.
      Note: If you want to see the cost allocation tags in Beam, activate the cost allocation tags in AWS. To activate the cost allocation tags, see Activating the AWS-Generated Cost Allocation Tags.
    2. Click Execute CloudFormation Template .
      The following success message is displayed.

      Successfully fetched the CloudFormation Template.

    3. If your organization's compliance requirements disallow to directly execute the CloudFormation Template in the AWS console, download the template by clicking the Download icon and get the template reviewed and approved internally.
      Upload the approved template when performing the steps to execute the template in the AWS console. For detailed instructions, see Executing Beam CloudFormation Template (AWS Console).
    4. Click the hyperlink Click here to execute CloudFormation Template if you have the permission to directly execute the CloudFormation Template in the AWS console. This redirects you to the AWS console.
      For detailed instructions, see Executing Beam CloudFormation Template (AWS Console).
    5. Click Verify and Save .
      Note: It takes 24 to 48 hours for the data to appear in Beam.
      Your AWS payer account is successfully configured in Beam.

What to do next

Once you configure your AWS payer account, Beam detects all the associated linked accounts. It is recommended to generate and execute the CFT for each linked account to optimize your cloud spend better. To configure linked accounts in Beam, see Configuring Linked Accounts.

Configuring Linked Accounts

Beam detects the AWS linked accounts after you add the payer account.

About this task

To view the list of AWS linked accounts, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > AWS Accounts . You can view the payer accounts added in Beam. Click Manage to view the list of linked accounts detected for a payer account.

To configure the linked accounts in Beam, do the following.

Procedure

  1. Click Configure against the linked account you want to configure.
  2. In the Account Configuration page, perform the following steps.
    1. Select the access type you want to grant to Beam.
      The available options are as follows.
      • Spend Analysis and Optimize Recommendations : This option is selected by default. You cannot clear this option. Beam requires read permissions for spend analysis and optimize recommendations.
      • Click to Fix and Playbooks : Selecting this access type would allow you to act on the saving insights, optimize the costs from the Beam console, create and invoke the Lambda function for Playbooks, and perform Eliminate actions.

      For more information, see Required Permissions.

      Optionally, check to enable Enable one-click policy updates to support upcoming features. . This option allows Beam to prepare the permission policy in case additional permissions are required for a feature. Once you select this option, you must update the policy for the account from the AWS Accounts page.
    2. Click Next to go to the Review Configuration page.
  3. In the Review Configuration page, perform the following steps.
    1. Review the information you entered in the Account Configuration page.
    2. Click Execute CloudFormation Template .
      The following success message is displayed.

      Successfully fetched the CloudFormation Template.

    3. If your organization's compliance requirements disallow to directly execute the CloudFormation Template in the AWS console, download the template by clicking the Download icon and get the template reviewed and approved internally.
      Upload the approved template when performing the steps to execute the template in the AWS console. For detailed instructions, see Executing Beam CloudFormation Template (AWS Console).
      Note: Make sure that you are logged on to the same linked account for which you created the CloudFormation template.
    4. Click the hyperlink Click here to execute CloudFormation Template if you have the permission to directly execute the CloudFormation Template in the AWS console. This redirects you to the AWS console.
      For detailed instructions, see Executing Beam CloudFormation Template (AWS Console).
      Note: Make sure that you are logged on to the same linked account for which you created the CloudFormation template.
    5. Click Verify and Save .
    Beam starts providing cost-saving recommendations for the linked account you just configured. If you just configured your payer account, it takes up to 24-48 hours for the cost data to be displayed in Beam.
    Repeat these steps for all the linked accounts for which you want to see cost recommendations. The best practice is to configure all the linked accounts to optimize your cloud spend better.
Removing Linked Accounts

This section describes the steps to unconfigure linked accounts.

About this task

To view the list of AWS linked accounts, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > AWS Accounts . You can view the payer accounts added in Beam. Click Manage to view the list of linked accounts detected for a payer account.

To unconfigure the linked accounts from the payer account, do the following.

Procedure

  1. Click Edit against the linked account you want to configure.
    The Account Configuration page appears.
  2. In the top-right corner of the page, click Remove ARN .
    By removing this IAM Role, you will limit the permissions that Beam has for this linked account.

    A confirmation message appears. Click Delete to complete the workflow.

    Figure. AWS Linked Account - Unconfigure Click to enlarge

Verifying AWS Account Configuration

After your AWS account configuration in Beam is complete, you can verify if the configuration is correct.

About this task

To test if your AWS account is accessible, do the following.

Procedure

  1. Log on to your AWS Management Console.
  2. In the drop-down menu, click My Billing Dashboard .
    Figure. AWS Management Console Click to enlarge My Billing Dashboard
  3. In the sidebar menu, click Cost &Usage Reports .
    Figure. AWS Management Console - AWS Cost and Usage Reports Click to enlarge AWS Cost and Usage Reports
    If you can create a report or a CUR report exists on this page, your AWS access is correct.
    Note: If a CUR report exists in the AWS Cost and Usage Reports page, you can also create a CUR report.

Creating Cost and Usage Report (AWS Console)

To create an AWS Cost and Usage Report (CUR), go to the Reports page of the AWS Billing and Cost Management Console .

About this task

The AWS Cost and Usage Report lists AWS usage for each service category used by an account and its IAM users in hourly or daily line items, as well as any tags that you have activated for cost allocation purposes. Beam requires the cost and usage details of the AWS resources to provide insights and cost-saving recommendations.

To create an AWS Cost and Usage Report, do the following.

Procedure

  1. Log on to your AWS Management Console.
  2. In the drop-down menu, click My Billing Dashboard .
    Figure. AWS Management Console - CUR Report Click to enlarge My Billing Dashboard
  3. In the sidebar menu, click Cost & Usage Reports . Then click Create report .
    Figure. AWS Management Console - CreateCUR Report Click to enlarge My Billing Dashboard
    The Report content page appears.
  4. In the Report name box, enter the name of the CUR and select Include resource IDs check box. Then click Next .
    Figure. AWS Management Console - Report content page Click to enlarge
    The Delivery options page appears.
  5. Click Configure to configure a S3 bucket.
    Note: Make sure to select time granularity as Hourly and compression type as GZIP .
    Figure. AWS Management Console - CUR (Configuring S3 bucket) Click to enlarge Cost and Usage Report
    The Configure S3 Bucket page appears. You can select an existing S3 bucket or create a S3 bucket.
  6. In the Configure S3 Bucket page, do one of the following.
    • In the Select existing bucket area, in the S3 bucket name list, select an existing S3 bucket. Then click Next .

      Or

    • In the Create a bucket area, enter a S3 bucket name and select the region where you want to create the S3 bucket. Then click Next .
    Figure. AWS Management Console - Configure S3 Bucket page Click to enlarge
    The Verify policy page appears.
  7. Select I have confirmed that policy is correct check box. Then click Save .
    Figure. AWS Management Console - Verify Policy page Click to enlarge
    Your S3 bucket gets configured.
  8. In the Report path prefix box, enter a report path prefix.
    This step is optional.
  9. Ensure that you set Time granularity to Hourly , Report versioning to Create new report version , and Compression Type to GZIP . Then click Next .
  10. Review the details and click Review and Complete to create the CUR.

Getting Cost and Usage Report (CUR) Details (AWS Console)

About this task

The AWS Cost and Usage Report lists AWS usage for each service category used by an account and its IAM users in hourly or daily line items, as well as any tags that you have activated for cost allocation purposes. Beam requires the cost and usage details of the AWS resources to provide insights and cost-saving recommendations. You can get the CUR details using the AWS Billing Dashboard.

To get the details of your existing CUR, do the following.

Procedure

  1. Log on to your AWS Management Console. Ensure that you have sufficient AWS Billing Dashboard permissions and S3 access.
  2. In the drop-down menu, click My Billing Dashboard .
    Figure. AWS Management Console - CUR Details Click to enlarge My Billing Dashboard
  3. In the sidebar menu, click Cost & Usage Reports .
  4. In the AWS Cost and Usage Reports table, find your CUR report name and S3 bucket.
  5. Copy the CUR report name and S3 bucket name you want to configure in Beam from the table.
    Figure. AWS Cost and Usage Reports table Click to enlarge Copy Required Details
  6. To extract the report path prefix, select the required CUR report name check box and click Edit .
    Figure. AWS Cost and Usage Reports table Click to enlarge Open Report
    The Report content page appears.
  7. Ensure that the time granularity selected is Hourly and Include resource IDs is checked. If not, create a CUR report.
    Figure. Report content page Click to enlarge Check the Report content values
  8. Scroll down the Report content page and locate Report path prefix . Copy the text present and paste it into the Beam console.
    Note: Make sure that the compression type is GZIP .
    Figure. Report content page Click to enlarge Paste in your prefix
  9. If the Report path prefix field is empty, then leave the Prefix section in the Beam console empty as well.

Executing Beam CloudFormation Template (AWS Console)

About this task

CloudFormation template allows you to provision and manage your AWS resources effortlessly. You can create templates for the service or application architectures you want and have AWS CloudFormation use those templates for quick and reliable provisioning of the services or applications.

To execute the CloudFormation template, do the following.

Procedure

  1. Log on to your AWS account and go to the Create stack page.
  2. In the Prepare template area, click Template is ready .
  3. In the Specify template area, select the relevant option based on the template's location.
    • Click Amazon S3 URL and enter the URL if you opted to directly execute the CloudFormation template. Then, click Next to proceed.

      Or,

    • Click Upload a template file if you opted to download the template from Beam for internal review purposes, or you choose to configure the payer account using API. Then, click Choose File to upload the template file that you downloaded. Click Next to proceed.
    Figure. AWS Management Console - Select Template Click to enlarge Execute Beam CloudFormation Template
  4. In the Specify stack details page, in the Stack name box, enter a stack name if you want to. Then click Next .
    Note: Do NOT modify any other information on this page.
    Figure. AWS Management Console - Specify Details Click to enlarge Give your stack a name
  5. In the Configure stack options page, scroll down to the bottom of the page and click Next .
    Figure. AWS Management Console - Configure stack options Click to enlarge Go to AWS CloudFormation
  6. In the Review page, scroll down to the bottom of the page and select I acknowledge that AWS CloudFormation might create IAM resources with custom names check box. Then click Create stack .
    Figure. AWS Management Console - Review Click to enlarge Review and create stack
  7. In the Events tab, wait for the message CREATE_COMPLETE .
    Figure. AWS Management Console - Events tab Click to enlarge Verify your stack
  8. Click Verify and Save on the Beam console.

Activating the AWS-Generated Cost Allocation Tags

The cost allocation tag is a label that AWS assigns to an AWS resource. You can use the cost allocation tags to track your AWS costs on a detailed level. After you activate the cost allocation tags, AWS uses the cost allocation tags to organize your resource costs on your cost allocation report. This makes it easier for you to categorize and track your AWS costs.

About this task

To activate the AWS-generated tags, do the following.

Procedure

  1. Log on to your AWS Management Console and go to the Billing and Cost Management Dashboard (https://console.aws.amazon.com/billing/home#/).
  2. In the sidebar menu, click Cost allocation tags .
  3. In the AWS-Generated Cost Allocation Tags area, click Activate .
    Note: It can take up to 24 hours for the tags to activate.

Getting Report Path Prefix (AWS Console)

While performing the AWS account onboarding in Beam, you need to enter the report path prefix that is appended to the name of your CUR. This section describes the steps to get the report path prefix for your CUR from the AWS console.

About this task

To get the report path prefix for your CUR, perform the following steps in the AWS console.

Procedure

  1. Log on to your AWS Management Console. Ensure that you have sufficient AWS Billing Dashboard permissions and S3 access.
  2. In the drop-down menu, click My Billing Dashboard .
    Figure. AWS Management Console - CUR Details Click to enlarge My Billing Dashboard
  3. In the sidebar menu, click Cost & Usage Reports .
    The AWS Cost and Usage Reports page appears. You can view a table that contains all the reports created in the AWS account.
  4. To get the report path prefix, select the required CUR report name check box and click Edit .
    Figure. AWS Cost and Usage Reports table Click to enlarge Open Report
    The Report content page appears.
  5. Scroll down the Report content page and locate Report path prefix . Copy the text present and paste it into the Beam console.
    Note: If the Report path prefix field is empty, then leave the Report Prefix field in the Beam console empty as well.
    Figure. Report content page Click to enlarge Paste in your prefix

Required Permissions

This section describes the read and read & write policies required by Beam.

Payer Account

  • Spend Analysis and Optimize Recommendations (read permissions)
    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Action": [
            "autoscaling:Describe*",
            "cloudfront:Get*",
            "cloudfront:List*",
            "opsworks:Describe*",
            "opsworks:Get*",
            "cloudtrail:DescribeTrails",
            "cloudtrail:GetTrailStatus",
            "cloudwatch:Describe*",
            "cloudwatch:Get*",
            "cloudwatch:List*",
            "dynamodb:DescribeTable",
            "dynamodb:ListTables",
            "ec2:Describe*",
            "ec2:GetReservedInstancesExchangeQuote",
            "elasticache:Describe*",
            "elasticbeanstalk:Check*",
            "elasticbeanstalk:Describe*",
            "elasticbeanstalk:List*",
            "elasticbeanstalk:RequestEnvironmentInfo",
            "elasticbeanstalk:RetrieveEnvironmentInfo",
            "elasticloadbalancing:Describe*",
            "elasticmapreduce:Describe*",
            "elasticmapreduce:List*",
            "redshift:Describe*",
            "elasticache:Describe*",
            "iam:List*",
            "iam:CreatePolicy",
            "iam:AttachRolePolicy",
            "iam:CreatePolicyVersion",
            "iam:DeletePolicyVersion",
            "iam:Get*",
            "workspaces:Describe*",
            "route53:Get*",
            "route53:List*",
            "rds:Describe*",
            "rds:ListTagsForResource",
            "s3:List*",
            "sqs:GetQueueAttributes",
            "sqs:ListQueues"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Effect": "Allow",
          "Action": [
            "s3:Get*",
            "s3:List*"
          ],
          "Resource": [
            "arn:aws:s3:::/*",
            "arn:aws:s3:::"
          ]
        },
        {
          "Effect": "Allow",
          "Action": [
            "s3:Get*",
            "s3:List*"
          ],
          "Resource": [
            "arn:aws:s3:::bucket-xyz/*",
            "arn:aws:s3:::bucket-xyz"
          ]
        },
        {
          "Effect": "Allow",
          "Action": [
            "organizations:ListAccountsForParent",
            "organizations:ListAccounts"
          ],
          "Resource": "*"
        }
      ]
    }
  • Click to Fix (read & write permissions)
    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Sid": "Stmt1415015011805",
          "Action": [
            "ec2:Describe*",
            "ec2:CreateSnapshot",
            "ec2:DeleteSnapshot",
            "ec2:DeleteVolume",
            "ec2:CreateTags",
            "ec2:ReleaseAddress",
            "ec2:RegisterImage",
            "ec2:CreateImage",
            "ec2:DeregisterImage",
            "ec2:DisassociateAddress",
            "ec2:TerminateInstances",
            "ec2:CreateImage",
            "ec2:ModifySnapshotAttribute",
            "ec2:ModifyInstanceAttribute",
            "ec2:GetReservedInstancesExchangeQuote"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Effect": "Allow",
          "Action": [
            "s3:Get*",
            "s3:List*"
          ],
          "Resource": [
            "arn:aws:s3:::/*",
            "arn:aws:s3:::"
          ]
        },
        {
          "Effect": "Allow",
          "Action": [
            "s3:Get*",
            "s3:List*"
          ],
          "Resource": [
            "arn:aws:s3:::bucket-xyz/*",
            "arn:aws:s3:::bucket-xyz"
          ]
        },
        {
          "Effect": "Allow",
          "Action": [
            "organizations:ListAccountsForParent",
            "organizations:ListAccounts"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015042420",
          "Action": [
            "elasticloadbalancing:DeleteLoadBalancer",
            "elasticloadbalancing:Describe*"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015086161",
          "Action": [
            "cloudtrail:DescribeTrails",
            "cloudtrail:GetTrailStatus"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015300839",
          "Action": [
            "rds:Describe*",
            "rds:List*",
            "rds:CreateDBSnapshot",
            "rds:DeleteDBSnapshot",
            "rds:DeleteDBInstance"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015300851",
          "Action": [
            "iam:CreatePolicy",
            "iam:AttachRolePolicy",
            "iam:CreatePolicyVersion",
            "iam:DeletePolicyVersion",
            "iam:List*",
            "iam:Get*"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Action": [
            "cloudtrail:ListTags",
            "cloudtrail:GetEventSelectors",
            "events:*",
            "sns:Set*",
            "sns:Get*",
            "sns:GetTopicAttributes",
            "sns:DeleteTopic",
            "sns:Create*",
            "sns:Unsubscribe",
            "sns:ConfirmSubscription",
            "sns:SetTopicAttributes",
            "sns:Subscribe",
            "sns:List*"
          ],
          "Resource": "*",
          "Effect": "Allow",
          "Sid": "Stmt1534849103503"
        },
        {
          "Sid": "Stmt1415015300878",
          "Action": [
            "autoscaling:Describe*"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611947000",
          "Effect": "Allow",
          "Action": [
            "redshift:Describe*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948000",
          "Effect": "Allow",
          "Action": [
            "cloudwatch:GetMetricStatistics",
            "dynamodb:DeleteTable"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948010",
          "Effect": "Allow",
          "Action": [
            "opsworks:Describe*",
            "opsworks:Get*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948020",
          "Effect": "Allow",
          "Action": [
            "route53:Get*",
            "route53:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948021",
          "Effect": "Allow",
          "Action": [
            "elasticache:Describe*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948022",
          "Effect": "Allow",
          "Action": [
            "elasticmapreduce:Describe*",
            "elasticmapreduce:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948023",
          "Effect": "Allow",
          "Action": [
            "dynamodb:Describe*",
            "dynamodb:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948025",
          "Effect": "Allow",
          "Action": [
            "elasticmapreduce:Describe*",
            "elasticmapreduce:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948024",
          "Effect": "Allow",
          "Action": [
            "elasticbeanstalk:Check*",
            "elasticbeanstalk:Describe*",
            "elasticbeanstalk:List*",
            "elasticbeanstalk:RequestEnvironmentInfo",
            "elasticbeanstalk:RetrieveEnvironmentInfo"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948028",
          "Effect": "Allow",
          "Action": [
            "cloudfront:Get*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948029",
          "Effect": "Allow",
          "Action": [
            "elasticache:Describe*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948030",
          "Effect": "Allow",
          "Action": [
            "config:Describe*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948035",
          "Effect": "Allow",
          "Action": [
            "cloudwatch:Describe*",
            "cloudwatch:Get*",
            "cloudwatch:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948036",
          "Effect": "Allow",
          "Action": [
            "cloudfront:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948076",
          "Effect": "Allow",
          "Action": [
            "kinesis:ListStreams"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948086",
          "Effect": "Allow",
          "Action": [
            "glacier:ListVaults"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948089",
          "Effect": "Allow",
          "Action": [
            "sqs:ListQueues",
            "sqs:GetQueueAttributes"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948088",
          "Effect": "Allow",
          "Action": [
            "workspaces:Describe*",
            "elasticache:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948092",
          "Effect": "Allow",
          "Action": [
            "lambda:CreateFunction",
            "lambda:TagResource",
            "lambda:InvokeFunction",
            "lambda:GetFunction",
            "lambda:ListAliases",
            "lambda:UpdateFunctionConfiguration",
            "lambda:GetFunctionConfiguration",
            "lambda:UntagResource",
            "lambda:UpdateAlias",
            "lambda:UpdateFunctionCode",
            "lambda:GetFunctionConcurrency",
            "lambda:ListTags",
            "lambda:DeleteAlias",
            "lambda:DeleteFunction",
            "lambda:GetAlias",
            "lambda:CreateAlias"
          ],
          "Resource": "arn:aws:lambda:*:*:function:*"
        },
        {
          "Sid": "Stmt1445611948093",
          "Effect": "Allow",
          "Action": [
            "lambda:ListFunctions",
            "iam:PassRole"
          ],
          "Resource": "*"
        }
      ]
    }

Linked Account

  • Optimize Recommendations (read permissions)
    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Action": [
            "autoscaling:Describe*",
            "cloudfront:Get*",
            "cloudfront:List*",
            "opsworks:Describe*",
            "opsworks:Get*",
            "cloudtrail:DescribeTrails",
            "cloudtrail:GetTrailStatus",
            "cloudwatch:Describe*",
            "cloudwatch:Get*",
            "cloudwatch:List*",
            "dynamodb:DescribeTable",
            "dynamodb:ListTables",
            "ec2:Describe*",
            "ec2:GetReservedInstancesExchangeQuote",
            "elasticache:Describe*",
            "elasticbeanstalk:Check*",
            "elasticbeanstalk:Describe*",
            "elasticbeanstalk:List*",
            "elasticbeanstalk:RequestEnvironmentInfo",
            "elasticbeanstalk:RetrieveEnvironmentInfo",
            "elasticloadbalancing:Describe*",
            "elasticmapreduce:Describe*",
            "elasticmapreduce:List*",
            "redshift:Describe*",
            "elasticache:Describe*",
            "iam:List*",
            "iam:Get*",
            "workspaces:Describe*",
            "route53:Get*",
            "route53:List*",
            "rds:Describe*",
            "rds:ListTagsForResource",
            "s3:List*",
            "sqs:GetQueueAttributes",
            "sqs:ListQueues"
          ],
          "Effect": "Allow",
          "Resource": "*"
        }
      ]
    }
  • Click to Fix (read & write permissions)
    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Sid": "Stmt1415015011805",
          "Action": [
            "ec2:Describe*",
            "ec2:CreateSnapshot",
            "ec2:DeleteSnapshot",
            "ec2:DeleteVolume",
            "ec2:CreateTags",
            "ec2:ReleaseAddress",
            "ec2:RegisterImage",
            "ec2:CreateImage",
            "ec2:DeregisterImage",
            "ec2:DisassociateAddress",
            "ec2:TerminateInstances",
            "ec2:CreateImage",
            "ec2:ModifySnapshotAttribute",
            "ec2:ModifyInstanceAttribute",
            "ec2:GetReservedInstancesExchangeQuote"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015042420",
          "Action": [
            "elasticloadbalancing:DeleteLoadBalancer",
            "elasticloadbalancing:Describe*"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015086161",
          "Action": [
            "cloudtrail:DescribeTrails",
            "cloudtrail:GetTrailStatus"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015300839",
          "Action": [
            "rds:Describe*",
            "rds:List*",
            "rds:CreateDBSnapshot",
            "rds:DeleteDBSnapshot",
            "rds:DeleteDBInstance"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015300851",
          "Action": [
            "iam:List*",
            "iam:Get*"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1415015300878",
          "Action": [
            "autoscaling:Describe*"
          ],
          "Effect": "Allow",
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611947000",
          "Effect": "Allow",
          "Action": [
            "redshift:Describe*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948000",
          "Effect": "Allow",
          "Action": [
            "cloudwatch:GetMetricStatistics",
            "dynamodb:DeleteTable"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948010",
          "Effect": "Allow",
          "Action": [
            "opsworks:Describe*",
            "opsworks:Get*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948020",
          "Effect": "Allow",
          "Action": [
            "route53:Get*",
            "route53:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948021",
          "Effect": "Allow",
          "Action": [
            "elasticache:Describe*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948022",
          "Effect": "Allow",
          "Action": [
            "elasticmapreduce:Describe*",
            "elasticmapreduce:List*"
          ],
          "Resource": "*"
        },
        {
          "Action": [
            "cloudtrail:ListTags",
            "cloudtrail:GetEventSelectors",
            "events:*",
            "sns:Set*",
            "sns:Get*",
            "sns:GetTopicAttributes",
            "sns:DeleteTopic",
            "sns:Create*",
            "sns:Unsubscribe",
            "sns:ConfirmSubscription",
            "sns:SetTopicAttributes",
            "sns:Subscribe",
            "sns:List*"
          ],
          "Resource": "*",
          "Effect": "Allow",
          "Sid": "Stmt1534849103503"
        },
        {
          "Sid": "Stmt1445611948023",
          "Effect": "Allow",
          "Action": [
            "dynamodb:Describe*",
            "dynamodb:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948025",
          "Effect": "Allow",
          "Action": [
            "elasticmapreduce:Describe*",
            "elasticmapreduce:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948024",
          "Effect": "Allow",
          "Action": [
            "elasticbeanstalk:Check*",
            "elasticbeanstalk:Describe*",
            "elasticbeanstalk:List*",
            "elasticbeanstalk:RequestEnvironmentInfo",
            "elasticbeanstalk:RetrieveEnvironmentInfo"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948028",
          "Effect": "Allow",
          "Action": [
            "cloudfront:Get*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948029",
          "Effect": "Allow",
          "Action": [
            "elasticache:Describe*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948030",
          "Effect": "Allow",
          "Action": [
            "config:Describe*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948035",
          "Effect": "Allow",
          "Action": [
            "cloudwatch:Describe*",
            "cloudwatch:Get*",
            "cloudwatch:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948036",
          "Effect": "Allow",
          "Action": [
            "cloudfront:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948076",
          "Effect": "Allow",
          "Action": [
            "kinesis:ListStreams"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948086",
          "Effect": "Allow",
          "Action": [
            "glacier:ListVaults"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948089",
          "Effect": "Allow",
          "Action": [
            "sqs:ListQueues",
            "sqs:GetQueueAttributes"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948088",
          "Effect": "Allow",
          "Action": [
            "workspaces:Describe*",
            "elasticache:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948091",
          "Effect": "Allow",
          "Action": [
            "s3:List*"
          ],
          "Resource": "*"
        },
        {
          "Sid": "Stmt1445611948092",
          "Effect": "Allow",
          "Action": [
            "lambda:CreateFunction",
            "lambda:TagResource",
            "lambda:InvokeFunction",
            "lambda:GetFunction",
            "lambda:ListAliases",
            "lambda:UpdateFunctionConfiguration",
            "lambda:GetFunctionConfiguration",
            "lambda:UntagResource",
            "lambda:UpdateAlias",
            "lambda:UpdateFunctionCode",
            "lambda:GetFunctionConcurrency",
            "lambda:ListTags",
            "lambda:DeleteAlias",
            "lambda:DeleteFunction",
            "lambda:GetAlias",
            "lambda:CreateAlias"
          ],
          "Resource": "arn:aws:lambda:*:*:function:*"
        },
        {
          "Sid": "Stmt1445611948093",
          "Effect": "Allow",
          "Action": [
            "lambda:ListFunctions",
            "iam:PassRole"
          ],
          "Resource": "*"
        }
      ]
    }

Azure Onboarding - Overview

The Azure account is a globally unique entity that gets you to access Azure services and your Azure subscriptions. You can create multiple subscriptions in your Azure account to create separation, for example, for billing or management purposes. You can configure your Azure account in Beam to enable cost visibility and optimization capabilities for your Azure cloud resources. Once you configure the Azure account, Beam fetches your Azure cost data and provides insights on cost and optimization. For detailed procedure about onboarding the following two Azure billing account types, see

  • Adding Azure Enteprise Agreement Account
  • Adding Azure Microsoft Customer Agreement (MCA) Account

Adding Azure Enteprise Agreement Account

This section describes the procedure to add your first Azure enterprise agreement account in Beam. Beam fetches the billing data of all projects associated with the given billing account and provides visibility into your spend.

Before you begin

Before attempting to add azure enterprise agreement account in Beam, make sure you satisfy the following requirements.
  • You must have enterprise administrator privileges.
  • You must have an owner access to the individual azure subscriptions.

About this task

To add your Azure account, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Azure Accounts .
  2. Click Connect Azure Account .
    Figure. Connect Azure Account Click to enlarge

    The Connect Azure Enrollment page appears.
  3. From the types of the Azure contract, choose Enterprise Agreement (EA) and click Next .
  4. Enter Enrollment Information .
    Enter a name for your enrollment, Enrollment Number , and Enrollment Access Key and click Next .
    • To know how to get your enrollment number, click How do I get enrollment number? and follow the instructions. Alternatively, see Capturing Enrollment Number (Azure Portal).
    • To know how to get your enrollment access key, click How do I get enrollment access key? and follow the instructions. Alternatively, see Capturing Enrollment Access Key (Azure Portal).
    Figure. Add Azure Account - Enrollment Information Click to enlarge

  5. Click Next .
    The App Configuration page appears.
  6. Enter App Configuration details.

    Beam uses the Azure Active Directory (AD) application to interact with Azure Portal.

    Note: Beam requires the AD configuration to receive your Azure infrastructure metadata. Beam uses this metadata to provide cost-saving recommendations.

    Enter the Domain Name , Tenant / Directory ID , Application ID , and Secret Key . Click How do I get it? to see on-screen instructions on getting the application configuration details from the Azure portal. Alternatively, see Configuring Azure App (Azure Portal).

    Note: Ensure that you enable multi tenancy for the application in the Azure portal.
    Figure. Add Azure Account - App Configuration Click to enlarge

    After you enter the required fields, click Next .
  7. Perform Role Assignment .

    Click Download Script to download the PowerShell script. Click How do I assign role? and follow the on-screen instructions to run the script in the Azure PowerShell . Alternatively, see Assigning Role (PowerShell).

    Ensure that you observe the guidelines related to the PowerShell script created by Beam. For more information, see PowerShell Script Guidelines.

    You can also assign roles manually. See Assigning Role (Without PowerShell).

  8. Check to enable I confirm I have executed the above powershell script and click Done .

    If the enrollment is successful, the enrollment and associated tenant and subscriptions get captured in Beam.

    Note:
      1. Application secret key activation may take up to 5 minutes.
      2. It takes a few hours for Beam to show your Azure cost data.

What to do next

Beam identifies all the Azure subscriptions associated with your Azure Enrollment and starts providing cost-saving recommendations for subscriptions for which you have owner access. If your enrollment has multiple tenants, add all those tenants to Beam. For more information, see Adding Azure Tenants.

To create a playbook for automating your regular workflows, you must configure an Azure Function App for your Enrollment account.

Adding Azure Subscriptions

You can create multiple subscriptions in your Azure account to create separation, for example, for billing or management purposes.

Before you begin

You must have Owner permission on the subscriptions you want to configure.

About this task

To add subscriptions to your Azure account, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Azure Accounts .
  2. Click Manage for the enrollment you want to add subscriptions.
  3. In the Actions column, click the plus icon for the tenant under which you want to add the subscription.
  4. In the Add Subscriptions page, click Download Script
  5. Perform Role Assignment .
    Click Download Script to download the PowerShell script. Click How do I assign role? and follow the on-screen instructions to run the script in the Azure PowerShell . Alternatively, see Assigning Role (PowerShell).
    Ensure that you observe the guidelines related to the PowerShell script created by Beam. For more information, see PowerShell Script Guidelines.
  6. Check to enable I confirm I have executed the above powershell script and click Done .

    Any subscription for which you have the owner access; and is not already configured in Beam is added in a few minutes.

Adding Azure Tenants

About this task

A tenant is an organization that owns and manages a specific instance of Azure cloud services. If your enrollment has multiple tenants, you can add all those tenants to Beam.

To add tenants to your Azure account, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Azure Accounts .
    You can view the enrollment accounts added in Beam.
  2. Click Manage against the enrollment account in which you want to add a tenant.
  3. Click Add Tenant under the enrollment account.
  4. Enter the Tenant / Directory ID and Domain Name .
    Click How do I get tenant information? follow the on-screen instructions to get the tenant information. Alternatively, see Retrieving Tenant Information (Azure Portal).
    Click Grant Permissions to grant permissions for this tenant. Clicking Grant Permissions redirects you to the Azure portal. On the Azure portal, log in to grant access to the application under the tenant.
    Note: You must have administrator access to the tenant to grant application permissions.
Verifying Azure Account Configuration

After your Azure account configuration in Beam is complete, you can verify if the configuration is correct.

About this task

To test if your Azure account is accessible, go to https://ea.azure.com/.

If you are able to access this page and no error message appears, your Azure access is correct.

Capturing Enrollment Number (Azure Portal)

About this task

To use the billing API, you need your Enrollment Number. It is the enrollment number that gets invoiced for total consumption.

To capture enrollment number, do the following.

Procedure

  1. Log on to your Azure Enterprise portal.
    Note: You must sign in as an enterprise administrator.
  2. Copy the Enrollment Number listed under Enrollment Detail .
    Figure. Azure Enterprise Portal - Enrollment Click to enlarge Capture Enrollment Number
  3. In the Beam console, in the Enrollment Number box, paste the value you copied.
Capturing Enrollment Access Key (Azure Portal)

About this task

You need the enrollment access key for authentication when using the billing APIs.

To capture the enrollment access key, do the following.

Procedure

  1. In the Azure Enterprise portal , go to Reports > Download Usage > API Access Key .
  2. Click generate if the key is not set or click expand key and copy the value.
    Note: Ensure that the key is active by checking Effective Date . Click regenerate to generate a new key.
    Figure. Azure Enterprise Portal - Reports Click to enlarge Capture Enrollment Access Key
  3. In the Beam console, in the Enrollment Access Key box, paste the value you copied.
Configuring Azure App (Azure Portal)

About this task

The Azure App Configuration service allows users to manage configuration within the cloud. You can create App Configuration stores to store key-value settings and consume stored settings from within applications, deployment pipelines, release processes, microservices, and other Azure resources.

To configure Azure app, do the following.

Procedure

  1. Log on to the Azure Portal, and go to Azure Active Directory .

    Azure Cloud - https://portal.azure.com/

    Azure Government Cloud - https://portal.azure.us/

    Figure. Azure Active Directory - Overview Click to enlarge Capture Domain Name
  2. Click Overview .
  3. Copy the domain name (available in the area marked as 3 in the figure) and paste it in Domain Name field in the Beam console.
  4. To capture Tenant/Directory ID, do the following.
    1. In the Azure Active Directory page, click Properties .
      Figure. Azure Active Directory - Properties Click to enlarge Capture Tenant/Directiory ID
    2. Copy the Directory ID and paste it in Tenant/Directory ID field in the Beam console.
  5. To capture the Application ID, do the following.
    1. In the Azure Active Directory page, click App registrations .
      Figure. Azure Active Directory - App registrations Click to enlarge Create App registrations
    2. Click New Registration .
    3. In the Create page, in the Name field, enter the application name.
      Figure. App registrations - Create page Click to enlarge Create App registrations
    4. In the Supported account types area, click Accounts in any organizational directory (Any Azure AD directory - Multitenant) .
      Note: You must select this option to support multiple tenants.
    5. In the Redirect URI (optional) area, select Web from the drop-down list and enter the URL as https://beam.nutanix.com for redirect URI, and click Create .
      Note: In the case of Azure Government cloud, enter the URL as https://beam.nutanix.us for redirect URI.
    6. Copy the Application ID and paste it in Application ID field in the Beam console.
      Figure. App registrations - Registered app page Click to enlarge Capture Application ID
  6. To capture the secret key, do the following.
    1. In the Registered app page that you just created, click Certificates & secrets .
    2. In the Client secrets area, click New client secret .
      The client secret is a secret string that the application uses to prove its identity when requesting a token.
      Figure. Certificates & secrets - creating client secret Click to enlarge Creating client secret
    3. In the Add a client secret page, in the Description box, enter a description for the client secret.
      Figure. Certificates & secrets - creating client secret Click to enlarge Creating client secret
    4. In the Expires area, click to select the expiry you want. Then click Add .
      The client secret value gets generated.
    5. Copy the generated client secret value and paste in the Secret Key field in the Beam console.
      Figure. Certificates & secrets - copying client secret Click to enlarge Copying client secret
Troubleshooting Azure App Configuration Step

When the Azure App configuration credentials provided in the Beam console fail during validation, you can perform the following steps to validate them.

About this task

To troubleshoot the Azure app configuration step failure, do the following.

Procedure

  1. Click the cloudshell button (marked as 1 in the figure) in the top-right section or click shell.azure.com.
    Note: In the case of Azure Government cloud, click the cloudshell button. The link shell.azure.com is not valid for the Azure Government cloud.
    Figure. Azure Enterprise Portal - Cloud Shell Click to enlarge Script Execution
  2. If you are launching Cloudshell for the first time, select PowerShell (marked as 2 in the figure).
  3. In the Subscription drop-down menu, select a subscription. Click Create Storage .
    Figure. Azure Enterprise Portal - Subscription Click to enlarge Script Execution
  4. Copy and paste the following command in PowerShell.
    az login --service-principal --tenant TENANT_ID -u APPLICATION_ID -p SECRET_KEY --allow-no-subscriptions
    • Replace the TENANT_ID , APPLICATION_ID , and SECRET_KEY with the actual values from your Azure Portal and press Enter to run the command.
      • If you do not see any error message, it means that the credentials you provided are valid and Beam should accept them. Go to the Beam console and click Next in the App Configuration step (step 4) . This should work without any error.
      • If you see an error message like Get Token request returned http error… , it means that the credentials you provided are invalid. And this mostly happens if the APPLICATION_ID and SECRET_KEY have not come into effect in Azure as it takes some time to propagate them.

        In such a case, it is recommended to wait for 2 to 5 minutes and then click Next in the App Configuration step (step 4) . This should work without any error.

Assigning Role (PowerShell)

About this task

This section describes how to assign roles using Azure PowerShell.
Note: The powershell script allows you to provide permission for multiple subscriptions as a bulk update.

To assign a role, do the following.

Procedure

  1. Click the cloudshell button (marked as 1 in the figure) in the top-right section or click shell.azure.com.
    Note: In the case of Azure Government cloud, click the cloudshell button (marked as 1 in the figure). The link shell.azure.com is not valid for the Azure Government cloud.
    Figure. Azure Enterprise Portal - Cloud Shell Click to enlarge Script Execution
  2. If you are launching Cloudshell for the first time, select PowerShell (marked as 2 in the figure).
  3. In the Subscription drop-down menu, select a subscription. Click Create Storage .
    Figure. Azure Enterprise Portal - Subscription Click to enlarge Script Execution
  4. After PowerShell is up, click Upload and select the file you downloaded.
    Figure. Azure Enterprise Portal - Powershell Click to enlarge Script Execution
  5. Execute the command : cd | ls
  6. Execute the uploaded script with the command : ./<file-name>.ps1
    Example: ./Beam-cg-roleProvision.ps1
    Ensure that you observe the guidelines related to the PowerShell script created by Beam. For more information, see PowerShell Script Guidelines.
Assigning Role (Without PowerShell)

You can manually assign roles from the Azure Portal. Log on to the Azure Portal (Azure Cloud - https://portal.azure.com/, Azure Government Cloud - https://portal.azure.us/) and go to the Subscriptions page.

About this task

Perform the following steps after the Configuring Azure App steps of the enrollment onboarding process.

Note: To perform the following steps, you must have at least owner permissions on the subscriptions for which you want to perform role assignment.

To manually assign roles, do the following.

Procedure

  1. In the Subscriptions page, select the subscription for which you want to perform role assignment.
    Figure. Subscriptions Page - Azure Portal Click to enlarge
  2. Click Access control (IAM) .
  3. Go to Role assignments .
  4. Click Add to open the Add role assignment page.
  5. In the Role drop-down list, select the role you want to assign.
    Beam at least needs Reader permissions to be able to provide cost savings recommendations successfully. Select the role as Contributor to perform eliminate operations from the Beam console.
  6. Select the application registered in the Active Directory.
  7. Click Save to complete the role assignment for the selected subscription.
    Repeat these steps to perform a role assignment for all of your subscriptions.
    Note: To complete the onboarding process, you must download the PowerShell script without which you cannot select I confirm I have executed the above powershell script (step 6 of Adding Azure Enteprise Agreement Account).
Retrieving Tenant Information (Azure Portal)

About this task

A tenant is an organization that owns and manages a specific instance of Azure cloud services. You need to add the tenant ID when performing the steps to add the Azure tenants in Beam.

To retrieve the tenant information, do the following.

Procedure

  1. Log on to the Azure Portal, and go to Azure Active Directory .
    Figure. Azure Active Directory - Overview Click to enlarge Capture Domain Name
  2. Click Overview .
  3. Copy the domain name (available in the area marked as 3 in the figure) and paste it in Domain Name field in the Beam Console.
  4. In the Azure Active Directory page, click Properties .
    Figure. Azure Active Directory - Properties Click to enlarge Capture Tenant/Directiory ID
  5. Copy the Directory ID and paste it in Tenant/Directory ID field in the Beam console.
Enabling Write Permissions for Azure Subscriptions

You can use the Edit Subscriptions option to grant write permissions for your subscriptions.

About this task

The following steps are involved when editing a subscription:
  • Select the check box in the Write column to grant write permissions for the subscriptions.
  • Perform role assignment.

To enable the write permissions for Azure subscriptions, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Azure Accounts .
    You can view the Azure Enrollments added in Beam.
  2. Click Manage against the Azure Enrollment that contains the subscription or subscriptions you want to edit.
    You can view a table that contains the tenants within the Azure Enrollment.
  3. In the Actions column, click the Edit Subscriptions icon against the tenant that contains your subscriptions.
    The Manage Subscriptions page appears.
    Figure. Azure Accounts page - Editing Subscriptions Click to enlarge Edit Azure Subscriptions
  4. In the Click to Fix and Playbooks column, select the check box to grant write permissions to the subscriptions.
    The available options are as follows.
    • Optimize Recommendations : This option is selected by default. You cannot clear this option. Beam requires read permissions for spend analysis and optimize recommendations.
    • Click to Fix and Playbooks : Selecting this access type would allow you to act on the saving insights, optimize the costs from the Beam console, deploy and invoke functions in an Azure Function App, and perform Eliminate actions.
  5. Perform Role Assignment .
    Click Download Script to download the PowerShell script. Click How do I assign role? and follow the on-screen instructions to run the script in the Azure PowerShell . Alternatively, see Assigning Role (PowerShell).
    Ensure that you observe the guidelines related to the PowerShell script created by Beam. For more information, see PowerShell Script Guidelines.
  6. Check to enable I confirm I have executed the above powershell script and click Done to complete.
PowerShell Script Guidelines

Beam simplifies onboarding using PowerShell scripts by eliminating the manual steps of permission and role assignments for multiple subscriptions.

Using PowerShell scripts helps you with the following.
  • Creates a role for Beam to access your Azure account.
  • Assigns the permissions to read the resources.
  • Provides access to API.

Observe the following guidelines related to the PowerShell script created by Beam.

  • Requirement of PowerShell script for Azure on-boarding - PowerShell script grants the necessary read permissions to the registered applications that Beam uses to fetch the inventory from the Azure Portal for cost savings recommendations.
  • Storage Account - Beam does not create any storage in Azure. To execute the PowerShell script, you must create a storage account in Azure to upload the script to the Cloud Shell.
  • Cost incurred by creating the storage account and uploading the script - Azure pricing for standard storage is $0.06 per GB/month. The size of the script that Beam provides is about 2 KB, so the storage cost of the script is negligible. When you create a storage account for the Cloud Shell, Azure creates a file share that contains a 5GB image that incurs charges. For more information, see Azure Cloud Shell documentation.
  • Resource Groups - Cloud Shell creates three resources when storage is created.
    • Resource group: cloud-shell-storage-<region>
    • Storage account: cs<uniqueGuid>
    • File share: cs-<user>-<domain>-com-<uniqueGuid>

    To avoid charges, delete the storage account after script execution.

Adding Azure Microsoft Customer Agreement (MCA) Account

This section describes the procedure to add your Azure MCA billing account in Beam. Beam fetches the billing data of all subscriptions associated with the given billing account and provides visibility into your spend.

Before you begin

Before attempting to add an Azure MCA billing account in Beam, make sure you satisfy the following requirements.
  • You must have an administrator privileges for adding an Azure MCA billing account in Beam.
  • You must have a Billing Account Owner permission for adding an Azure MCA billing account.
  • You must have or create an Azure AD application in the same tenant where the Azure MCA billing account exists.

About this task

To add your Azure MCA billing account, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Azure Accounts .
  2. Click Connect Azure Account .
    Figure. Connect Azure Account Click to enlarge

    The Connect Azure Account page appears.
  3. From the types of the Azure contract, choose Microsoft Customer Agreement Account (MCA) and click Next .
  4. In the MCA Account Information page.

    Enter the Account ID and a name for your MCA billing account.

    To know how to get your account ID from the Azure portal, click Read our documentation to see the on-screen the instructions. Alternatively, see Capturing MCA Billing Account ID (Azure Portal).

    Figure. Add Azure MCA Billing Account Information Click to enlarge

  5. Click Next .
    The App Configuration page appears.
  6. To enter your Azure Active Directory (AD) application details, do one of the following:
    • From the Use Existing Application drop-down, select an existing application.
    • Click Create a New App button to create a new Azure application.

    Beam uses the Azure AD application to interact with the Azure portal and to fetch billing, purchase, and pricing data.

    For the on-screen instructions on how to create an Azure AD application, click Read our documentation .

  7. If you select Create a New App , enter the App Name , Client ID , Secret Key , and Tenant ID to configure a new Azure application.

    For the on-screen instructions on how to get the application configuration details from the Azure portal, click How do I get client id? , How do I get secret key? , or How do I get tenant id? . Alternatively, see Configuring Azure MCA App (Azure Portal)

    Figure. Add Azure MCA Billing Account - App Configuration Click to enlarge

  8. After you enter the required fields, click Next .
  9. Perform Role Assignment .
    Note: Before you perform Step 10, ensure that the application you just created has a Billing account reader access on the given Azure MCA billing account in order to fetch billing information.

    To provide the necessary permissions on the Azure portal, click Read our documentation to see on-screen instructions. Alternatively, see Assigning Billing Account Reader Role (Azure Portal).

  10. Select the I confirm I have provided the relevant permissions checkbox and click Save. .

    If the Azure MCA billing account is onboarded successfuly, the associated subscriptions get captured in Beam.

    Note: It takes upto 24 hours for Beam to show your Azure cost data and capture the associated subscriptions.

What to do next

Beam identifies all the Azure subscriptions associated with your Azure MCA billing account and you can configure these subscriptions in Beam to see the cost savings recommendations.
Capturing MCA Billing Account ID (Azure Portal)

About this task

To use the billing API, you need your Azure MCA billing account ID. It is the unique identifier for your billing account that gets invoiced for total consumption.

To capture the account ID, do the following.

Procedure

  1. Log on to the Microsoft Azure portal and go to Cost Management + Billing .
    Note: You must have a Billing Account Owner permission for adding an Azure MCA billing account.
  2. In the left navigation pane, click Billing Scopes to open page for that option in the pane to the right.
    The Azure portal displays the list of billing accounts for which you have an access.
  3. Select the Azure MCA billing account that you want to onboard to Beam.
  4. In the left navigation pane, go to Settings and click Properties .
  5. Copy the ID listed under the General tab.
    Figure. Azure MCA Billing Account ID Click to enlarge
  6. In the Beam console, in the Account ID box, paste the value that you copied.
Configuring Azure MCA App (Azure Portal)

About this task

The Azure App Configuration service allows users to manage configuration within the cloud. You can create App Configuration stores to store key-value settings and consume stored settings from within applications, deployment pipelines, release processes, microservices, and other Azure resources.

To configure Azure app, do the following.

Procedure

  1. Log on to Microsoft Azure Portal and go to Azure Active Directory .
    Figure. Azure Active Directory - Overview Click to enlarge
  2. In the left navigation pane, go to App registrations and click New Registration .
  3. In the Register an application page, in the Name field, enter a display name for your application.
    Figure. Azure MCA App Registration Click to enlarge
  4. In the Supported account types area, click Accounts in this organizational directory only (Nutanix only - Single tenant) .

    For now, Beam supports only single tenant application.

  5. Do not change anything in the Redirect URI (optional) area.
  6. Click Register to complete the initial registration.

    The Azure portal displays the corresponding application's Overview pane.

  7. Copy the Display name , Application (client) ID , and Directory (tenant) ID (available in the area marked as 2 and 3 in the figure) and paste it in respective fields in the Beam console.
    Figure. Azure Application Overview Pane Click to enlarge
  8. To capture the secret key, do the following.
    1. In the App registration page, select the application that you just created.
    2. Go to Certificates & secrets > Client secrets and click New client secret .
      The client secret is a secret string that the application uses to prove its identity when requesting a token.
      Figure. Certificates & secrets - creating client secret Click to enlarge
    3. In the Add a client secret page, in the Description box, enter a description for the client secret.
    4. In the Expires area, click to select the expiry you want. Then click Add .
      Note: The client secret validity is limited to 24 months or less. You cannot specify a custom validity longer than 24 months.
      The client secret value gets generated.
    5. Copy the generated client secret value as it is never displayed again after you leave this page.
      Figure. Certificates & secrets - copying client secret Click to enlarge
      Note: If the client secret key is expired, you need to regenerate the key as specified in Step 8.
    6. Paste in the Secret Key field in the Beam console.
Assigning Billing Account Reader Role (Azure Portal)

This section describes how to assign the Billing account reader role to the application from the Azure Portal.

About this task

Perform the following steps after the Configuring Azure MCA App (Azure Portal) steps of the MCA onboarding process.

Note: To perform the following steps, you must have at least a Billing Account Owner permission for the application you want to perform role assignment.

To assign Billing account reader role, do the following.

Procedure

  1. Log on to the Azure Portal and go to the Cost Management + Billing page.
  2. In the left navigation pane, click Billing scopes and select an Azure MCA billing account for which you want to perform role assignment.
    Figure. MCA Billing Account Click to enlarge
  3. Click Access control (IAM) to open page for that option in the pane to the right.
  4. Click Add to open the Add permission page.
  5. In the Role drop-down list, select the role Billing account reader .
    Beam needs Billing account reader permissions to be able to fetch billing, purchase, and pricing data.
  6. Select the application registered in the active directory.
  7. Click Save to complete the role assignment for the selected application.
Managing Azure MCA Subscriptions and Applications

This section describes how to provide granular permissions at a subscription level to enable optimization and click-to-fix actions and manage your Azure AD applications.

Before you begin

You must have atleast an owner permission for the subscriptions you want to configure.

About this task

To configure subscriptions and manage applications of your Azure MCA billing account in Beam, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Azure Accounts .
    You can view the Azure Enrollments and MCA billing accounts added in Beam.
  2. Click Manage against the Azure MCA billing account that contains the subscription or subscriptions you want to edit.
    A table that contains the subscriptions within the Azure MCA billing account is displayed.
    Figure. Azure MCA Subscriptions Click to enlarge

  3. To enable a permission for the selected subscription, do the following.
    Note: Beam now allows you to configure permissions for the multiple subscriptions as a bulk update. For more details, see Modifying Azure MCA Billing Account, Applications and Subscriptions.
    1. In the Subscription tab, click any subscription or the down arrow key (on the right corner of the each row) for which you want to configure permissions.

      You can also search for the subscription by typing its name in the search box.

      Figure. Congfigure Permission for MCA Subscription Click to enlarge

      The available options are as follows.
      • Visibility : This option is enabled by default. You cannot edit or clear this option.
      • Optimization : Selecting this permission type would allow you to see the saving opportunities on unused and underutilised resources.
      • Click to Fix : Selecting this permission type would allow you to act on the saving insights and optimize the costs from the Beam console ( Eliminate actions).
    2. In the Actions column, click the Configure icon against the permission (Optimization or Click to Fix) you want to enable.
      The Configure Permissions page appears.
    3. Do one of the following.
      • From the Use Existing Application drop-down, select an existing application.
      • Click Create a New App button to create a new Azure application.
    4. If you select Create a New App , enter the App Name , Client ID , Secret Key , and Tenant ID to configure a new Azure application.

      For the on-screen instructions on how to get the application configuration details from the Azure portal, click How do I get client id? , How do I get secret key? , or How do I get tenant id? . Alternatively, see Configuring Azure MCA App (Azure Portal)

    5. Click Download Script to download the PowerShell script to grant permissions for your subscriptions.

      To run the script in Azure PowerShell , click How do I execute the script? and follow the on-screen instructions. Alternatively, see Assigning Role (PowerShell).

      You can also assign roles manually. For more details, see Assigning Role (Without PowerShell)

    6. Select the I confirm I have executed the above powershell script checkbox and click Save .
      Repeat these steps to assign both the permissions for all the required subscriptions.
      Note: To complete the onboarding process, you must download the PowerShell script without which you cannot select I confirm I have executed the above powershell script .
  4. To manage your Azure AD application, select the Azure AD App tab.

    A table that contains the applications is displayed.

    Figure. Azure AD Applications Click to enlarge

    1. Select the application for which you want to modify the details.
    2. In the Actions columns, do the following as desired.
      • Modify the application details by clicking the Edit button.

        A Edit Azure App pop-up window appears allowing you to update the App Name , Client ID , Secret Key , and Tenant ID .

        For the on-screen instructions on how to get the application configuration details from the Azure portal, click How do I get client id? , How do I get secret key? , or How do I get tenant id? . Alternatively, see Configuring Azure MCA App (Azure Portal)

        Click Save when you are done.

      • Delete the application by clicking the Delete button.

        Click Delete in the confirmation pop-up window.

Modifying Azure MCA Billing Account, Applications and Subscriptions

This section describes how to modify the Azure MCA billing account, application details, and configure permissions for multiple subscriptions within the Azure MCA billing account as a bulk update for billing or management purposes.

Before you begin

You must have atleast an owner permission for the subscriptions you want to configure.

About this task

To modify an Azure MCA billing account, applications and subscriptions details, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Azure Accounts .
    You can view the Azure Enrollments and MCA billing accounts added in Beam.
  2. Click Manage against the Azure MCA billing account that contains the subscription or subscriptions you want to edit.
    A table that contains the subscriptions within the Azure MCA billing account is displayed.
    Figure. MCA Subscriptions - Actions Click to enlarge

  3. On the top-right corner, click Actions to display the drop-down menu.
  4. To the configure permission for multiple subscriptions as a bulk update, click Configure Subscriptions from the drop-down menu and do the following.

    In the Edit permission for Subscriptions page, the permissions and entries for the subscriptions are displayed.

    Figure. Configure Permissions - Bulk Update Click to enlarge

    1. Choose the permission under Update Configuration .
    2. Select the checkbox for the subscriptions you want to update configuration and click Next .

      You can also search for the subscription by typing its name in the search box.

    3. Do one of the following.
      • From the Use Existing Application drop-down, select an existing application.
      • Click Create a New App button to create a new Azure application.
    4. If you select Create a New App , enter the App Name , Client ID , Secret Key , and Tenant ID to configure a new Azure application.

      For the on-screen instructions on how to get the application configuration details from the Azure portal, click How do I get client id? , How do I get secret key? , or How do I get tenant id? . Alternatively, see Configuring Azure MCA App (Azure Portal)

    5. Click Download Script to download the PowerShell script to grant permissions for your subscriptions.

      To run the script in Azure PowerShell , click How do I execute the script? and follow the on-screen instructions. Alternatively, see Assigning Role (PowerShell).

      You can also assign roles manually. For more details, see Assigning Role (Without PowerShell)

    6. Select the I confirm I have executed the above powershell script checkbox and click Save .
      Note: To complete the onboarding process, you must download the PowerShell script without which you cannot select I confirm I have executed the above powershell script .
  5. To modify the application name, click Edit Account Name from the Actions drop-down menu and do the following
    1. In the Change Account Name pop-up window, update the name as desired.
    2. Click the Save button.
  6. To modify the application details, click Edit Azure Application from the Actions drop-down menu and do the following.
    1. In the Edit Azure App pop-up window, update the App Name , Client ID , Secret Key , and Tenant ID .

      For the on-screen instructions on how to get the application configuration details from the Azure portal, click How do I get client id? , How do I get secret key? , or How do I get tenant id? . Alternatively, see Configuring Azure MCA App (Azure Portal)

    2. Click the Save button.
  7. To delete your MCA billing account, click Delete MCA Account from the Actions drop-down menu.

    Click Delete in the confirmation pop-up window.

Assigning Role (PowerShell)

About this task

This section describes how to assign permissions for Azure MCA billing account using Azure PowerShell.
Note: The powershell script allows you to provide permission for multiple subscriptions as a bulk update.

To assign a permission, do the following.

Procedure

  1. Click the cloudshell button (marked as 1 in the figure) in the top-right section or click shell.azure.com.
    Figure. Azure Portal - Cloud Shell Click to enlarge
  2. If you are launching Cloudshell for the first time, select PowerShell (marked as 2 in the figure).
  3. In the Subscription drop-down menu, select a subscription. Click Create Storage .
  4. After PowerShell is up, click Upload and select the file you downloaded.
    Figure. Azure Portal - Powershell Click to enlarge
  5. Execute the command : cd | ls
  6. Execute the uploaded script with the command : .\<file-name>.ps1
    Example: .\Beam-cg-roleProvision.ps1
Assigning Role (Without PowerShell)

This section describes how to manually assign permissions from the Azure Portal.

About this task

Perform the following steps after you configure the Azure MCA application as mentioned in the Configuring Azure MCA App (Azure Portal) section of the onboarding process.

Note: To perform the following steps, you must have at least owner permissions on the subscriptions for which you want to perform role assignment.

To manually assign roles, do the following.

Procedure

  1. Log on to the Azure Portal and go to the Subscriptions page.
  2. In the Subscriptions page, select the subscription for which you want to perform role assignment.
    Figure. Role Assignment - Azure Portal Click to enlarge
  3. In the left navigation pane, click Access control (IAM) to open page for that option in the pane to the right..
  4. Click Add to open the Add role assignment page.
  5. In the Role drop-down list, select the role you want to assign.
    Beam at least needs Reader permission to be able to provide cost savings recommendations successfully and Contributor permission to perform eliminate operations from the Beam console.
  6. Click Next .
  7. Click Select members and from the selected members drop-down list, choose the application registered in the Active Directory.
    Figure. Select Memebers Click to enlarge
  8. Click Select to complete the role assignment for the selected subscription.
    Repeat these steps to perform a role assignment for all of your subscriptions.
    Note: To complete the onboarding process, you must download the PowerShell script without which you cannot select I confirm I have executed the above powershell script .

Beam Gov(US) Cost Governance

Beam Gov(US) is an isolated instance running in AWS GovCloud (US) region to cater specific regulatory compliance requirements of the US government agencies at federal, state, and local levels, government contractors, educational institutes, and other US customers who run sensitive workload in AWS GovCloud and Azure Government Cloud, and want to bring Cost Governance for their cloud infrastructure, gain visibility, optimize and control their spend. Beam Gov(US) provides a single plane consolidated view for Cost Governance.

The onboarding process for Beam Gov(US) users differs from the onboarding process for commercial account users.
  • Separate Beam instance is deployed in the AWS GovCloud region (US-West) with a separate login URL for Beam Gov(US) users.
  • Beam Gov(US) supports the cost governance for AWS, Azure, GCP, and Nutanix On-premises in the GovCloud.
  • Beam Gov(US) also supports commercial cloud accounts along with the GovCloud.
Note: Beam Gov(US) Cost Governance is an early access feature. For more information, contact Nutanix Support .

Beam Gov(US) Sign up

The Beam Gov(US) sign up includes two steps.
  1. Beam Gov(US) Sign up Request Approval - The sign up request approval process involves the following steps.
    • Sign-up Request

      Contact the sales team expressing an interest in using Beam Gov(US).

    • Customer Verification

      The request is forwarded for verification to the Nutanix GovCloud Security team. As part of the verification, you will receive a form through DocuSign that you must fill and send back.

    • Beam Account Activation

      Once the request passes through the verification, Customer Service initiates the account creation process, and the primary user is notified with login details through an email. The email contains verification link, upon verifying email, the user can login to the Beam Gov(US).

  2. Account Registration Completion - In the Beam Gov(US) login page, create a password and select a timezone. Then login into the Beam console. You can enable or disable the MFA from the Profile page in the Beam console. For more information on enabling or disabling the MFA, see User Management.

GovCloud Account Configuration

After your Beam Gov(US) signup is complete, you can start onboarding your GovCloud account in Beam.

AWS GovCloud Onboarding

In AWS, a GovCloud account is always attached to a commercial account. This commercial account can be a linked account or a payer account.

Note: An AWS GovCloud account is always associated with one AWS commercial account for billing and payment purposes. All your AWS GovCloud billing is billed or invoiced to the associated AWS commercial account. You can view the AWS GovCloud account activity and usage reports through the associated AWS commercial account only.

To start with adding the GovCloud account in AWS, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > AWS Accounts .

You can view the list of AWS commercial accounts. You can click Add Gov Account against the commercial account to which you associated your GovCloud account. The Add AWS Account page appears.

The steps to add a GovCloud account is the same as to add an AWS commercial account. To add your GovCloud account, see Adding AWS Account (step 6 to step 10) .

After you complete the steps to add the GovCloud account, you can view the GovCloud account linked to the commercial account.

Figure. Configure - AWS GovCloud Account Click to enlarge Adding AWS GovCloud account

Azure Government Account Onboarding

In the case of Azure Government account onboarding, the steps are the same as commercial account onboarding.

Make sure that you select US Government Cloud to add a GovCloud account in the Enrollment Type list.

Figure. Configure - Azure Government Account Click to enlarge Adding Azure Government account

For the remaining step-by-step details, see Adding Azure Account.

User Management

You can add and manage users for GovCloud using the Beam console.

You can perform the following operations in Beam Gov(US).
  • Add a user

    To go to the User Management page, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > User Management . To add a user, see Adding a Beam User.

    In the case of AWS user management, the user may have access to the commercial account but no access to the GovCloud account linked to the commercial account. To give AWS GovCloud account access to a user, you must select the GovCloud account linked to the commercial account.

    Figure. User Management - GovCloud Account Click to enlarge Access to GovCloud Account
  • Resetting Password and MFA Management
  • Configuring Single Sign-On

Resetting Password and MFA Management

You can reset your password and enable or disable MFA from the Profile page in the Beam console.

About this task

To go to the Profile page, click the user drop-down menu on the top-right corner and select Profile .

To change your password, click the Change Password link.

Figure. Profile Page - Change Password Link Click to enlarge Change password link

To enable MFA, do the following.

Procedure

  1. In the Profile page, click the Enable MFA link.

    The Enable Multi-factor Authentication page appears.

  2. Do one of the following.
    • Scan the QR code by using the virtual MFA application (Google or Microsoft Authenticator).
    • Click the secret code link to get the secret code. Enter the secret code in your virtual MFA application.
      Figure. Enable Multi-factor Authentication Page Click to enlarge Enabling MFA

      The virtual MFA application starts generating codes.

  3. Enter the codes in Code 1 and Code 2 boxes. Then click Set MFA to enable MFA.

    To disable MFA, click the Disable MFA link in the Profile page.

    In the case your MFA device is lost or not accessible, click Login via OTP (for lost MFA)? link. Beam sends an OTP to your registered email id. Enter the OTP to login to Beam.

    Figure. Beam Login Page - Lost MFA Link Click to enlarge

Configuring Single Sign-On

The following section describes how to configure the single sign-on feature for Beam Gov(US).

About this task

To configure the single sign-on feature, do the following.

Procedure

  1. Log on to the Beam Console.
  2. Click the user drop-down menu on the top-right corner and select Single Sign On .
  3. In the Single Sign On page, in the Application Id box, enter the application id.
    Note: To get the Application Id, contact Nutanix Support .

    A success message appears, displaying that the single sign-on is successfully configured.

  4. Log out from the Beam Console to go to the login page.
  5. In the Login page, click Login with Single Sign On .
  6. In the Email box, enter your email id.
    In the case of conflict, while logging through the email address, you can click Try with Application ID to login with the application id.
  7. Click Login .

    You are redirected to your organization’s single sign-on application page.

    Enter your credentials and login to Beam Gov(US).

Getting Started With Configurations

After you onboard your cloud accounts in Beam, the following information becomes available for you to consume:
  • Dashboard – Get a graphical view of your overall spend, spend analysis, Reserved Instances (RI) utilization, and spend efficiency.
  • Analyze – Provides a deep visibility into your projected and current spend and allows you to drill down cost further based on your services, accounts, or application workload.
  • Reports – Automatically generated reports help you to track cost consumption across all your cloud accounts.
  • Purchase – Provides RI purchase recommendations based on your resource utilization patterns.
The following are the configurations to perform so that you can begin controlling your cloud consumption:
  • Saving Opportunities – After configuring the AWS payer account, ensure that you add the associated linked accounts in Beam to get cost optimization recommendations. For more information, see Configuring Linked Accounts.

    After configuring the Azure account, ensure that you add all the tenants within your account in Beam for maximum savings recommendations. For more information, see Adding Azure Tenants.

  • Create Business Units and Cost Centers for Chargeback – You can define a business unit by combining a group of cost centers. Chargeback is built on the business unit and cost center configuration construct that you define for the resources across all your cloud accounts.
  • Budgeting - A budget allows you to centralize the budget at the business unit, cost center, or scope levels to ensure that your consumption is within the budget that you have defined.
  • Custom Reports - You can create a customized report by aggregating and filtering using various native cloud dimensions and attributes to get insights on cloud usage and cost.
  • Playbooks - You can create a playbook to schedule action on your cloud resources and automate regular workflows. For example, you can shut down your test environments during non-business hours.
  • Scope - A scope is a logical group of your cloud resources that provides you with a custom view of your cloud resources. You can define scopes using cloud, accounts, and tags.
  • Integrations - You can integrate Beam with third-party applications such as Slack and ServiceNow. For example, integrate Beam with Slack to get notifications on your Slack channels.

AWS Cost Configuration

Beam allows you to define configuration settings for your cloud cost data. Cost Configuration is a set of rules that allow you to update cost inputs manually, and also select cost presentation options, allocation model options, and reporting rules that define how the cost of cloud resources get reported in Beam.

Beam provides you with multiple options when performing AWS cost configuration to let you choose how you want to present the cloud spend in Beam.

The options provided are as follows:
  • Cost Logic - You can choose between Amortized Cost or Absolute Cost.
  • Billing - You can choose between blended cost and unblended cost.
  • Credits and Refunds - You can either choose to include or exclude the credits and refunds in the cost report.
  • AWS EDP - You can either choose to include or exclude the EDP discount in the cost report.

All cost presented through Beam is generated depending on the options you select.

Cost Logic - Amortized Cost and Absolute Cost

The Cost Logic selection is applicable for determining how AWS RI, Savings Plan, EDP, Credits, Refunds, and Taxes get reported in Beam.

Amortized Cost Logic
Cost reporting is based on accrual-based accounting. For Reserved Instances (RI) and savings plan, the cost reporting is based on the effective cost column in the AWS CUR. For EDP, Credits and Refunds, and Taxes, Beam does the amortization calculation.

In the case of taxes, AWS reports the amortized cost of the tax at the account level. Beam does the amortization calculation at the service, region, resource level, and so on.

The Amortized Cost logic is useful in cases where you want to view the cost of resources on an accrual basis considering the usage of RI, Savings Plan, Discounts, and Taxes specific to that resource.

Absolute Cost Logic
Cost reporting is based on cash-based accounting. The RIs, savings plan, EDP, Credit and Refunds, and Taxes are not amortized over the billing period.

If you select the Absolute Cost option as the cost logic, the cost of RI, Savings Plan, EDP, Credits and Refunds is shown as a separate line item, and cloud resource cost is reported without the apportioned cost of RI, Savings Plan, and so on. This results in a spike on the day monthly RI fee or upfront RI fee gets charged.

Billing - Blended Cost and Unblended Cost

You can select between blended cost and unblended cost.

Unblended Cost
If you select the Unblended Cost option, Beam reports the cost of resources based on usage. Selecting this option reports the cost of resources from the Unblended Cost column in the AWS CUR.
Blended Cost
If you select the Blended Cost option, Beam reports the cost of resources based on the average cost of usage across the consolidated billing family. Selecting this option reports the cost of resources from the Blended Cost column of the AWS CUR.
Note: If you select the Amortized Cost as the cost allocation basis, the Blended Cost option for billing cannot be selected.

Credits and Refunds

Beam provides you with the option to include or exclude the credits and refunds in the cost report irrespective of the Amortized Cost or Absolute Cost selection.

If you select the Include option, Credits and Refunds are shown in the cost report as a separate line item or amortized and apportioned to a resource depending on the selection between the absolute cost or amortized cost, respectively.

If you select the Exclude option, Credits and Refunds are not shown in the cost report to the user (for example, Scope or Cost Center viewers). It also gets excluded from the Analyze page.

AWS Enterprise Discount Program (AWS EDP)

AWS provides enterprises a discount on its services against a volume spend commitment. For example, an enterprise commits to spending $2 million on AWS services and receives a certain percentage of the discount. The enterprise must pay $2 million even if they do not spend the amount.

Beam provides you with the option to include or exclude the EDP discount in the cost report. EDP discount is applicable to both amortized and absolute cost logic.

If you select the Include option, EDP discount is shown in the cost report as a separate line item or amortized and apportioned to a resource depending on the selection between the absolute cost or amortized cost, respectively. If you select the Exclude option, EDP discount is not shown in the cost report to the user (for example, Scope or Cost Center viewers). It also gets excluded from the Analyze page.

You can add the EDP contract details in Beam. Adding the EDP contract details allows you to view the projected spend after the EDP discount in the Analyze page. Any discount from EDP from the current usage gets reported in CUR and Beam reports accordingly.

For future projections, you need to add contract details which Beam uses for projection.

Configuring the AWS Cost Logic

This section provides the steps to configure the AWS cost logic. The cost report gets generated according to the logic you configure. Also, the configured logic applies to all the available views in Beam.

About this task

To configure the AWS cost logic, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > AWS Cost Configuration .
    The AWS Cost Configuration page appears.
    Figure. Configure Cost - AWS Click to enlarge
  2. In the Cost Logic area, select Amortized Cost or Absolute Cost .
    The Cost Logic selection determines how AWS RI, Savings Plan, EDP, Credits, Refunds, and Taxes get reported in Beam. For more information, see Cost Logic - Amortized Cost and Absolute Cost .
  3. In the Billing area, select Unblended Cost or Blended Cost .
    If you select Unblended Cost , Beam reports the cost of resources based on usage. If you select Blended Cost , Beam reports the cost of resources based on the average cost of usage across the consolidated billing family.
    Note: If you select Amortized Cost as the cost logic, the Blended Cost option for billing cannot be selected.
  4. In the Credits and Refunds area, select Include or Exclude .
    • Include - Includes the credits and refunds data in the cost report for historical spend.
    • Exclude - Excludes the credits and refunds data in the cost report for historical spend.
  5. In the Enterprise Discount Program (EDP) area, select Include or Exclude .
    • Include - Includes EDP discount in the cost report for projected spend. You need to add your EDP contract details (step 7).
    • Exclude - Excludes EDP discount from the cost report for projected spend.

    For more information, see AWS Enterprise Discount Program (AWS EDP) .

  6. In the EDP area, click Add EDP Contract to add your EDP contract details.
    The Add Details for an AWS EDP Contract page appears.

    AWS provides enterprises a discount on its services against a volume spend commitment. Adding the EDP contract details in Beam allows you to view the projected spend after the EDP discount in the Analyze page.

    Do the following:

    1. In the Payer Account list, select the payer accounts under your EDP discount contract.
    2. In the EDP Contract Start Date box, select the contract start date.
    3. In the EDP Term list, select the EDP term according to your contract.
      The Yearly Discounts area appears. You can add different discounts for each year according to your EDP contract.
    4. Click Save to save your contract details and close this page.

    You can add multiple EDP contracts. Also, you can click Manage against an EDP contract to change the contract details.

  7. Click Save to apply the AWS cost logic.
    The configured logic applies to all the available views in Beam.

Currency Configuration

Configure currency to view the cloud spend in your preferred currency.

The currency configuration reduces the ambiguity in analyzing cloud spend from different cloud providers who often provide billing data in different currencies. For example, GCP might report cloud consumption in INR while AWS report cloud consumption in USD. Consolidating the billing data from these different sources without considering currency type results in ambiguous reports and dashboards. In order to simplify multicloud cost governance, Beam allows you to configure a single currency to calculate spend data across all views. You can also configure the corresponding conversion rates for the configured currency or use dynamic rates that Beam provides.

Source currency

Source currency is the currency that your cloud service provider reports billing. When you onboard multiple cloud billing accounts from different cloud providers or regions, you can see a consolidated list of all the source currencies in the respective billing data on the Currency Configuration page. If you onboard a GCP billing account reported in INR and an AWS payer account reported in USD, you will see INR and USD in the source currency list.

Target currency

Target currency is the preferred functional currency for your organization to view spend analysis across Beam in. All the spend data shown in Beam is also converted to this currency. Beam uses the target currency to provide a unified cost view when you onboard multiple cloud accounts with different source currencies. Furthermore, this configuration gives you the flexibility to set a single currency for the following views.
  • Multicloud views such as All-Clouds , Financial (Business Unit or Cost Center), or Scopes
  • Cloud overviews such as GCP Overview , AWS Overview , or Azure Overview

Currency conversion

When you select target currency, you must also select the conversion rates applicable for the selected currency. Beam supports the following currency conversion types.
  • Dynamic Currency Conversion : Beam uses the third-party API from https://exchangeratesapi.io/ to ingest the conversion rates for the corresponding source currencies.
    Note: Beam uses the conversion rate for the first of every month to calculate spend for the entire month. If the conversion rate for the first of every month is unavailable, Beam uses the last fetched monthly rates to calculate spend for that month.
  • Custom Defined Currency Conversion : Beam uses the user-defined exchange rate to calculate historic and projected spend data across all days/months/years.

Configuring Currency and Conversion Rates

You can use this configuration to select the target currency and the corresponding conversion rates applicable for spend analysis across Beam.

About this task

After you configure target currency, you see the following across Beam.
  • Spend data in the target currency for all cloud overview and mulitcloud views.
  • A currency toggle to select between source currency and target currency for individual cloud accounts.
For more information on general guidelines and considerations, see Currency Configuration Considerations .

To configure the currency, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu and then go to Configure > Currency .
    The Currency Configuration page appears.
    Figure. Configure Currency Click to enlarge
  2. Click View Source Currencies to view the list of source currencies corresponding to the cloud resource billing data.
  3. Under Target Currency , select the preferred currency in the drop-down list.
    For example, if you select AMD Armenian Dram , costs across Beam reports in AMD.
  4. In the Currency Conversion area, do one of the following to configure the conversion rates applicable for the selected currency.
    • To automatically fetch the currency exchange rates, click Dynamic Currency Conversion . Additionally, click View to see the ingested exchange rates for the last 12 months.
      Note: Currency exchange rates are updated by Nutanix on a monthly basis. Currency exchange rates are provided as estimates and for informational purposes only. The rates and conversion estimates should not be relied on for invoiced billing conversions by cloud service providers.
      Click to enlarge
    • To manually define the currency exchange rates, click Custom Defined Currency Conversion and then click Customize .

      In the text box, enter the exchange rates as shown in the following figure.

      Click to enlarge
  5. Click Save to apply the currency configuration.
    The configured currency applies to all the available views in Beam.

Currency Configuration Considerations

Limitations and guidelines to consider when using the currency configuration.

Dashboard

  • The Reserved Instances widget on the Dashboard always reports with source currency across all AWS and Azure views.
  • By default, Beam provides the spend data in the target currency.
  • The currency toggle is available when you select individual cloud accounts in the view selector.
  • The currency toggle is not available when you select cloud overview or multicloud views in the view selector.
  • The currency toggle is not available when the configured target currency is same as the source currency.

Analyze

  • By default, Beam provides the spend data in the target currency.
  • The currency toggle is available when you select individual cloud accounts in the view selector.
  • The currency toggle is not available when you select cloud overview or multicloud views in the view selector.
  • The currency toggle is not available when the configured target currency is same as the source currency.
  • The reports in the Analyze page is in the currency that is selected at the time of report generation.
    • If you select source currency in the toggle, and then click download, share, or schedule, the reports are in the source currency.
    • If you select target currency in the toggle, and then click download, share, or schedule, the reports are in the configured target currency.
      Note: If you modify the target currency after scheduling the reports, Beam always uses the target currency that is configured at the time of generating the schedule reports. For example, if the target currency is INR while scheduling the reports. And you modify the target currency as GBP, then Beam generates the scheduled reports in GBP.
    • If the currency toggle is not available, the reports you download, share, or schedule are in the configured target currency.

Chargeback

  • By default, Beam provides the spend data in the target currency. The currency toggle is not available in Chargeback .
  • The system report (Global Chargeback Report) that you can download, share, or schedule is in target currency that is configured at the time of report generation.

Budget

  • By default, Beam provides the spend data in the target currency. The currency toggle is not available in Budget .
  • Beam shows the allocated cost of the budget in the target currency.

Reports

  • System reports are in target currency that is configured at the time of report generation. If the target currency configuration is INR and you modify the target currency to GBP after 4 weeks. The system reports generated weekly are in INR for week 1, week 2, week 3, and week 4. The system reports generated for week 5 are in GBP as the target currency at the time of report generation is GBP.
    Note: The following reports are in source currency.
    • Daily reports: New EC2 RI Recommendation report and EC2 RI Utilization Report
    • Monthly reports: Expired RI Report , Expiring RI Summary Report , and On Demand vs Reserved Hours Cost
  • The currency in the Custom reports is based on the configuration in the create or edit page. The reports are in either source currency or target currency as configured while creating the reports.

Save

  • By default, Beam provides the spend data in the target currency.
  • The currency toggle is available when you select individual cloud accounts in the view selector.
  • The currency toggle is not available when you select cloud overview or multicloud views in the view selector.
  • The currency toggle is not available when the configured target currency is same as the source currency.
  • The system report (Cost Optimization Detailed Report) that you can download, share, or schedule in the Save page is in target currency that is configured at the time of report generation.
  • The drill-down reports that you can download, share, or schedule in any of the tabs on the Save page uses the selection in the currency toggle.
    • If you select source currency in the toggle, and then click download, share, or schedule, the reports are in the source currency.
    • If you select target currency in the toggle, and then click download, share, or schedule, the reports are in the configured target currency.
    • If the currency toggle is not available, the reports you download, share, or schedule are in the configured target currency.
    Figure. Save Click to enlarge

Purchase

Beam uses the source currency provided in the billing data for assessing reserved instances and displays the data in source currency. Beam does not use the target currency provided in the currency configuration page for assessing reserved instances.

Cloud Account Onboarding

  • When you onboard your first cloud account, Beam configures the source currency as the default target currency with Dynamic Currency Conversion rates.
  • When you onboard a cloud account with new currency and the currency conversion is Custom Defined Currency Conversion . Beam adds the latest dynamic currency conversion rate as a custom defined conversion rate for the new currency.

Dashboard

The following sections describe the dashboard view for your cloud accounts (AWS, Azure, or GCP), business units and cost centers (financial view), All Clouds (multicloud), and scopes.

Dashboard (AWS)

The Dashboard provides a snapshot of your overall spend, spend analysis, Reserved Instances (RI) utilization, and spend efficiency.

Dashboard Views

To view the AWS dashboard, log on the Beam console and select any of the connected AWS accounts.
Note: Beam provides a toggle to view spend data in your preferred currency. You can select the currency toggle at the top right to switch between target and source currency. For information on general guidelines and considerations, see Currency Configuration Considerations .
Spend Overview
Displays a pie graph of the cost breakup summary and spend trends across AWS accounts and services. By default, this view displays the spending summary of all the services linked to your AWS account. To view a cost summary of all the linked accounts in your AWS payer account, click the drop-down list at the top-right corner of the widget and select Accounts . To view details for your overall spend, click View All .
Figure. Spend Overview Widget Click to enlarge []
Spend Analysis
Displays a bar graph of the historical spend analysis for the selected period with an estimated and actual spend for the current month. By default, this view displays the monthly projection for the spend analysis. You can change the default view to display daily or quarterly projections. To view the analytics detail, click View Cost Analysis .
Figure. Spend Analysis Widget Click to enlarge []
Reserved Instances
Displays a line chart of the RI utilization summary of EC2 instances for the selected period and provides statistics for average and current RI coverage. You can hover over the chart to view the RI usage of a specific day. You can change the default view to display the EC2 and RDS RI top recommendation. To view the recommendations, click the View More button.
Note: Beam always uses the source currency provided in the billing data for assessing reserved instances and displays the data with source currrency. Beam does not use the target currency provided in the currency configuration page for assessing reserved instances.
Figure. Reserved Instances Widget Click to enlarge
Spend Efficiency
Displays a line chart of the cost optimization efficiency for the selected period and provides statistics for potential savings, unused resources, and resizeable resources. To view the optimization details, click View Potential Savings .
Figure. Spend Efficiency Widget Click to enlarge

You can also create a custom report to analyze the cost. To generate a custom report, click Build Custom Report at the bottom of the screen. For more information, see Creating Custom Reports (AWS).

Dashboard (Azure)

The dashboard for Azure provides a holistic overview of your overall Azure spend.

Azure dashboard enables you to do the following cost management tasks.

  • View monthly usage charges.
  • Compare current and previous month Azure cost.
  • Review cost projections (month and year).
To view the Azure dashboard, log on the Beam console and select any of the connected Azure accounts.
Note: Beam provides a toggle to view spend data in your preferred currency. You can select the currency toggle at the top right to switch between target and source currency. For information on general guidelines and considerations, see Currency Configuration Considerations .
Table 1. Dashboard (Azure)
View Description
Spend Overview Provides the total cost of services and subscriptions for your Azure account. You can change the view of the graph by switching between Services and Subscription views. The graph displays the top four costing services and subscriptions, and the remaining gets grouped under Others . To view the details of the cost, click the View All button, which redirects you to the Analyze page.
Spend Analysis Provides the cost trends distributed over the period. You can view the spend analysis based on the Daily or Monthly filters. To view the details of the cost, click the View Cost Analysis button, which redirects you to the Analyze page.
Top Resource Groups Provides the cost associated with the resource groups in your Azure infrastructure. This widget displays the top four costing resource groups and groups the remaining cost under Others . Click the Monthly or Daily selector icons to see monthly or daily views. To view the details of your selection, click the View All button, which redirects to the Analyze page.
Spend Efficiency

The spend efficiency widget displays the spending efficiency as percentage for the last seven days. The spend efficiency value helps to identify how well the Azure resources are getting utilized.

The spend efficiency widget also shows the cost optimization opportunities as Potential Savings , Unused Resources , and Resizable Resources . To the optimization details, click the View Potential Savings button, which redirects you to the Save page.

Dashboard (GCP)

The GCP dashboard provides you a summarized and graphical view of your overall GCP spend across the billing accounts and resources. The dashboard provides you the current spends and projections of your GCP cloud resources.

To view the GCP dashboard, log on the Beam console and select any of the connected GCP accounts.
Note: Beam provides a toggle to view spend data in your preferred currency . You can select the currency toggle at the top right to switch between target and source currency. For information on general guidelines and considerations, see Currency Configuration Considerations.
Figure. Dashboard - GCP Click to enlarge
Table 1. Dashboard Views
View Description
Spend Overview - Projects Displays a pie chart of the spend breakup summary by GCP projects for the current month to date. To view details for your overall spend, click View Details , which redirects you to the Analyze page .
Spend Analysis Displays a bar chart of the historical spend analysis along with the summarized spend data based on the selected period.
  • Daily : Displays the average daily cost and cumulative spend data of the last seven days.
  • Monthly : Displays the estimated spend, actual spend, and variance. Variance is calculated based on the actual spend of the previous term and projected spend of the current term.
  • Quaterly : Displays the current year and projected yearly spend. Quaterly projections are not available when you select GCP Overview from the View Selector .
By default, this view displays the monthly projection for the spend analysis. You can change the default view to display daily or quarterly projections. To view the analytics details, click View Cost Analysis ,which redirects you to the Analyze page .
Spend Overview - Services Displays a pie chart of the spend breakup summary by GCP services for the current month to date. To view details for your overall spend, click View Details , which redirects you to the Analyze page .
Spend Overview - Usage Type

Displays a pie chart of the spend breakup summary by GCP usage types for the current month to date. To view details for your overall spend, click View Details , which redirects you to the Analyze page.

GCP Compute Engine allows you to purchase committed use contracts in return for discounted prices for VM usage. You can purchase compute resources at a discounted price in return for committing to paying for those resources for one year or three years.

Dashboard (Multicloud)

Dashboard provides a snapshot of your overall spend, spend analysis, and spend efficiency.

This section provides detail for the following views - All Clouds , Financial , and Scopes . Click View in the top-right corner to open the View Selector and select different views.

Dashboard Views

To view the multicloud dashboard, log on the Beam console and select any of the multicloud views— All Clouds , Financial , and Scopes .
Note: Currency toggle is not available for multicloud views. You can view the spend data in target currency on the multicloud dashboad. You can select the target currency in the currency configuration page. For more information on general guidelines and considerations, see Currency Configuration Considerations .
Spend Overview
Displays a pie graph of the cost breakup summary and spend trends across AWS, Azure, GCP, and Nutanix accounts and services within the business unit, cost center, or scope you select. By default, this view displays the spending summary of all the services within your business unit, cost center, or scope. To view a cost summary of all the linked accounts in your business unit or cost center, click the drop-down list at the top-right corner of the widget and select Accounts . To view details for your overall spend, click View Details , which redirects you to the Analyze page.
Figure. Spend Overview Widget Click to enlarge
Spend Analysis
Displays a bar graph of the historical spend analysis for the selected period with an estimated and actual spend for the current month. By default, this view displays the monthly projection for the spend analysis across across AWS, Azure, GCP, and Nutanix accounts and services. You can change the default view to display the daily projection. To view the analytics detail, click View Cost Analysis , which redirects you to the Analyze page.
Figure. Spend Analysis Widget Click to enlarge
Save
Displays a pie graph of the total savings realized by eliminating or optimizing AWS and Azure resources. To view the details of your total savings, click the View Potential Savings button, which redirects you to the Save page.
Figure. Save Widget Click to enlarge
Cloud Spend Efficiency (All Clouds view)
The cloud spend efficiency widget displays the spending efficiency for your AWS and Azure clouds as a percentage for the last seven days. The spend efficiency value helps to identify how well cloud resources are getting utilized. You can hover over the line graph for the AWS and Azure clouds to view the total spend, optimized spend, and potential savings information.
Figure. Cloud Spend Efficiency Widget Click to enlarge
Budget (Financial and Scopes views)
Displays a bar graph of the actual spend, budgeted spend, and estimated spend for each quarter. To view the details of your budget, click the View Details button, which redirects you to the Budget page.
Figure. Budget Widget Click to enlarge

Analyze - Cost Analysis

Analyze allows you to drill down into your cloud spend, slice, and dice all the cloud cost data. You can analyze each cloud in detail across accounts, services, purchase options, and other different attributes. You can analyze data historically across days and past months.

Beam not only provides spend analytics on past data but uses its in-built algorithms to report on the spend anomalies, and forecast future spend patterns. This projection is available for the current month and next 6 months across accounts or services.

To view the Analyze page, click the Hamburger icon in the top-left corner to display the main menu. Then, click Analyze . Click View in the top-right corner to open the View Selector Pop-up and select the Cloud , Financial , or Scope view you want. The view selected from Dashboard , Report , Save , or Purchase gets persisted in Analyze and defaults to the last selected view.

Figure. Analyze Click to enlarge

The Analyze page displays the following:

  • Details according to the view you select.
    • All Clouds - shows detail for all the cloud accounts (AWS, Azure, GCP, and Nutanix) added in your Beam account.
    • Cloud Accounts ( AWS , Azure , and GCP ) - shows detail for the selected cloud account.
    • Financial - shows detail for the business unit or cost center you select.
    • Scopes - shows detail for the custom scopes you select.
  • Graphical and tabular view of spend data. The top portion of the Analyze page displays a graphical view of your data. The bottom portion of the Analyze page displays a tabular view of your spend data.
    Note:
    • By default, each view displays values in a line chart form. You can change the default view to a pie chart or bar graph.
    • The spend data for the last 2-3 days is faded-out in the chart and table. Because the data in the billing files from the cloud provider is generally incomplete for 2-3 days.
    • Beam displays the date and time it last updated the spend data at the top-right corner of the Analyze view. Beam updates spend data every 6 hours. However, Beam skips updating, if the data ingested from the cloud providers is the same since the last update.
  • Deep visibility into your historical, current, and projected spend based on the time period selected. You can use the drop down menus on the tab to display the spend information by time period ( Day or Month ).
  • Customized view of your spend data according to the selected filter options. To create a filter, you can select the required options under Filters and click Apply . For more information about filters, see Filtering Options .
  • Schedule, share, and download customized reports under each view.
  • Cumulative spend analysis. To visualize the cumulative spend data, you can turn on the Cumulative toggle.
  • Anomaly detection. Beam analyzes the spending trend on your subscribed resources and reports cost spikes in your cloud accounts. For more information, see Anomaly Detection .
    Note: Beam supports anomaly detection for AWS and Azure cloud accounts only. Anomaly detection feature is not supported for GCP and Nutanix on-prem accounts.

How Spend Projection Works

Beam considers the last 150 days of cost data starting from T-3 days (T is the current date) and applies ML algorithms to project the cost for upcoming 6 months. The algorithms run daily and provide future cost projections.

In case the data is available for less than 150 days, Beam considers the available data to project the cost. If the cost data is not available, Beam shows the projected spend as zero. Beam starts displaying the projected spend as soon as data becomes available.

Cost Analysis (AWS)

Analyze allows you to track cost consumption across all your cloud resources at both the aggregate and granular level. You can drill down cost further based on your services, accounts, or application workload.

Analyze Views

This view provides deep visibility into your projected and current spend. Analyze displays a line chart to project cost consumption that helps you view and analyze your cost and usage across your organization.

To view the AWS cost analysis, select Analyze from the main menu. Then, click View in the top-right corner to open the View Selector and select AWS .

Note:
  • Beam provides a toggle to view spend data in your preferred currency. You can select the currency toggle at the top right to switch between target and source currency. For information on general guidelines and considerations, see Currency Configuration Considerations .
  • You can schedule, share, or download reports under each view except for the Hourly time unit and custom time range. For more information, see Cost Reports.
  • You can create filters at the view level, and then apply filters to display the line chart according to the selected filter options. To create a filter, you can select the required options under Filters and click Apply . For more information about filters, see Filtering Options .

    Other subscriptions charges filter - Subscription charges apart from RI charges and Marketplace charges. For example, APN annual fees.

  • If you want to see the cost allocation tags in Beam, activate the cost allocation tags in AWS. You can use the cost allocation tags to track your AWS costs on a detailed level. To activate the cost allocation tags, see Activating the AWS-Generated Cost Allocation Tags.
Current Spend
The current spend view provides the current AWS cost and its breakdown based on the different usage and resource data.
Table 1. Current Spend
View Description
Overview Displays the total AWS spend (subscription charges and taxes).
Accounts Displays the total cost of the linked accounts in your AWS payer account.
Cost Centers Displays the total spend grouped by Beam cost centers. This view includes the unallocated costs that are not tagged in your AWS account.
Charge Types Displays the total spend grouped by the AWS line item type. For example, credit, fee, tax, usage and so on.
Services Displays the total spend grouped by services. By default, this view displays the cost breakup of the top five services that are used the most in your AWS account.
Regions Displays the total cost grouped by regions.
API Operation Displays the total cost of all the API operation requests on your AWS services.
Purchase Option Displays the breakup of Reserved, Unused Reservation, Savings Plan, Unused Savings Plan, Spot and On Demand Cost.
Tags Displays the total cost based on the service tag applied to your AWS resources. You can click the tag drop-down list to select a service tag.
Projected Spend

The projected spend view provides insight into the actual and projected cost for the selected period. You can select different time ranges from the Time range drop-down list in the Filters option.

Table 2. Projected Spend
View Description
Overview Displays a line chart of the projected and actual spend for the selected period.
Accounts Displays a line chart of the projected and actual spend for all the linked accounts in your AWS account.
Services Displays a line chart of the projected and actual spend of the top five services that are used the most in your AWS account.

You can track and set alerts for your AWS cloud budget. To set alerts, click Configure Budget Alerts at the top-right corner of the view. For more information, see Configuring Budget Alerts .

Compute

The Compute view provides the cost specific to all the compute resources configured on AWS. For example, EC2-Instance, EC2-NAT Gateway.

Table 3. Compute
View Description
Overview Displays a line chart of the total spend for all the compute resources for the selected period. You can hover over the stacked bar to view the total spend for a specific day.
Account Displays a line chart of the total cost for all the linked accounts in your AWS payer account.
Cost Centers Displays the total spend grouped by Beam cost centers. This view includes the unallocated costs that are not tagged in your AWS account.
Charge Types Displays the total spend grouped by the AWS line item type. For example, credit, fee, tax, usage and so on.
Sub Services Displays a line chart of the total cost for all the sub-services activated in your AWS account.
Instances Displays a line chart of the total cost for all the instances purchased.
Instance types Displays a line chart of the total cost according to your instance type.
Tags Displays a line chart of the total cost based on the service tag applied to your AWS resources. You can click the tag drop-down list to select a service tag.
Database
The Database view provides the cost specific to your database services configured on AWS. For example, RDS, PostgreSQL.
Table 4. Database
View Description
Overview Displays a line chart of the total spend for all your database services configured in your AWS account for the selected period. You can hover over the stacked bar to view the total spend for a specific day.
Accounts Displays a line chart of the total cost for all the linked accounts in your AWS payer account.
Cost Centers Displays the total spend grouped by Beam cost centers. This view includes the unallocated costs that are not tagged in your AWS account.
Charge Types Displays the total spend grouped by the AWS line item type. For example, credit, fee, tax, usage and so on.
Sub Services Displays a line chart of the total cost for all the sub-services activated in your AWS account.
Instances Displays a line chart of the total cost for all the instances purchased.
DB Engines Displays a line chart of the total cost for all the database engines.
Instance types Displays a line chart of the total cost according to the instance type purchased.
Tags Displays a line chart of the total cost based on the service tag applied to your AWS resources. You can click the tag drop-down list to select a service tag.
Storage
The storage view provides the cost specific to your storage resources running on AWS. For example, S3.
Table 5. Storage
View Description
Overview Displays a line chart of the total spend for all your storage resources running on AWS for the selected period. You can hover over the stacked bar to view the total spend for a specific day.
Accounts Displays a line chart of the total storage cost for all the linked accounts in your AWS payer account.
Cost Centers Displays the total spend grouped by Beam cost centers. This view includes the unallocated costs that are not tagged in your AWS account.
Charge Types Displays the total spend grouped by the AWS line item type. For example, credit, fee, tax, usage and so on.
Sub Services Displays a line chart of the total storage cost split for all the sub-services activated in your AWS account.
Buckets Displays a line chart of the total storage cost grouped by all the buckets created in your AWS accounts.
Tags Displays a line chart of the total cost based on the service tag applied to your AWS resources. You can click the tag drop-down list to select a service tag.
Data Transfer
The Data Transfer view provides the cost specific to all the data transfer across your AWS services. For example, Intra Region Transfer.
Table 6. Data Transfer
View Description
Overview Displays a line chart of the total spend incurred for all the data transfer across your AWS services for the selected period. You can hover over the stacked bar to view the total spend for a specific day.
Accounts Displays a line chart of the total cost for all the linked accounts in your AWS payer account that you are analyzing.
Services Displays the total cost for all the services activated in your AWS account.
Regions Displays a line chart of the total cost incurred in moving data according to the AWS regions.
Resources Displays a line chart of the data transfer cost grouped by the resources.
Tags Displays a line chart of the total cost based on the service tag applied to your AWS resources. You can click the tag drop-down list to select a service tag.

Cost Analysis (Azure)

Beam allows you to analyze your projected and current Azure cloud spends. Beam makes this planning process easy using machine intelligence and recommendation algorithms that analyze your workload patterns.

To view the Azure cost analysis, select Analyze from the main menu. Then, click View in the top-right corner to open the View Selector and select Azure .

Note:
  • Beam provides a toggle to view spend data in your preferred currency. You can select the currency toggle at the top right to switch between target and source currency. For information on general guidelines and considerations, see Currency Configuration Considerations .
  • You can schedule, share, or download reports under each view except for the custom time range. For more information, see Cost Reports.
  • You can create filters at the view level, and then apply filters to display the line chart according to the selected filter options. To create a filter, you can select the required options under Filters and click Apply .For more information about filters, see Filtering Options.

The Analyze page has the following tabs.

Current Spend
The current spend view provides the current Azure cost and its breakdown based on the different usage and resource data.
Table 1. Current Spend
View Description
Overview Actual and projected overall cost for the selected period.
Subscriptions Cost of subscriptions on your Azure account.
Cost Centers Total spend grouped by Beam cost centers. This view includes the unallocated costs that are not tagged in your Azure account.
Services Cost of Azure services based on the service category like data management, networking, and storage.
Service Types Cost based on the type of Azure service you consume.
Regions Cost based on the region in which the resource is hosted.
Azure Cost Centers Cost based on the configured Azure cost centers.
Department Cost based on the configured department.
Resource Groups Cost based on the configured resource group.
Tags Cost based on the tags applied on the Azure resources.
Projected Spend

The projected spend view provides insight into the actual and projected cost for the selected period. You can select different time ranges from the Time range drop-down list in the Filters option.

Table 2. Projected Spend
View Description
Overview The total cost of Azure billing accounts.
Subscriptions The actual and projected cost for the chosen Azure subscription for the selected period.
Services Cost of Azure services based on the service category like data management, networking, and storage.
Virtual Machine
The virtual machine view provides the Azure cost specific to the Virtual Machine (VM) resource type.
Table 3. Virtual Machine
View Description
Overview Monthly or daily total usage cost for the VMs running on Azure.
Sub Services Monthly or daily split cost for the VM usage based on the different flavors of the VM.
Cost Centers Monthly or daily grouped by Beam cost centers. This view includes the unallocated costs that are not tagged in your Azure account.
Regions Monthly or daily cost for the usage based on the regions in which the VMs are deployed.
Resource IDs Monthly or daily cost for the usage based on the resource IDs of the VMs.
Storage
The storage view provides the cost specific to your storage resources running on Azure. For example, Files, General Block Blob.
Table 4. Storage
View Description
Overview Monthly or daily total usage cost for the storage resource running on Azure.
Sub Services Monthly or daily split cost for the VM usage based on the different types of storage option configured.
Cost Centers Monthly or daily grouped by Beam cost centers. This view includes the unallocated costs that are not tagged in your Azure account.
Regions Monthly or daily cost for the usage based on the regions in which the storage resources are deployed.
Resource IDs Monthly or daily cost for the usage based on the resource IDs of the storage option.
Data Services
The Data Services option provides the cost specific to your database services configured on Azure.
Table 5. Data Services
View Description
Overview Monthly or daily total usage cost for the database service running on Azure.
Sub Services Monthly or daily split cost for the VM usage based on the different types of database service configured.
Cost Centers Monthly or daily grouped by Beam cost centers. This view includes the unallocated costs that are not tagged in your Azure account.
Regions Monthly or daily cost for the usage based on the regions in which the database service is configured.
Resource IDs Monthly or daily cost for the usage based on the resource IDs of the database service.

Cost Analysis (GCP)

Analyze allows you to drill down into your cloud spend, slice and dice all the cloud cost data. You can analyze the GCP cloud spend in detail across projects, services, usage types, regions, and other attributes. You can analyze data historically across days and past months.

Beam not only provides spend analytics on past data but uses its in-built algorithms to forecast future spend patterns. This projection is available for the current month and next six months across projects or services.

To view the GCP cost analysis, select Analyze from the main menu. Then, click View in the top-right corner to open the View Selector and select GCP .

Analyze provides cost analysis capability for the GCP Billing account and the Project that you select from the View Selector . The view that you select from Dashboard and Report gets persisted in Analyze and defaults to the last selected view.

Note:
  • Beam provides a toggle to view spend data in your preferred currency . You can select the currency toggle at the top right to switch between target and source currency. For information on general guidelines and considerations, see Currency Configuration Considerations .
  • Schedule, share, and download reports under each view. For more information, see Cost Reports.
  • Create and apply filters to visualize the spend data according to the selected filter options. To create a filter, you can select the required options under Filters and click Apply . For more information about filters, see Filtering Options .

    The Folder list displays the information in the Project/Folder/Sub-folder format. For example, 952341568867/664245889765/897640334598 .

Current Spend

The current spend view provides the current GCP cost and its breakdown based on the different usage and resource data.

Table 1. Current Spend
View Description
Overview

Displays the total GCP spend.

You can view the total spend for each day or month. Use the drop-down list in the top-right corner of the page to select Day or Month .

Projects Displays the total spend grouped by Projects associated with the GCP billing account.
Cost Centers Displays the total spend grouped by cost centers defined in Beam. This view includes the unallocated costs that are not tagged in your GCP billing account.
Charge Types Displays the total spend grouped by the GCP line item type.
Service Types Displays the total spend grouped by service type. For example: network, compute, and storage.
Services Displays the total spend grouped by services.
Usage Types Displays the total spend grouped by usage types. For example: OnDemand and Commit1Yr.
Regions

Displays the total spend grouped by regions.

Note: A region is a specific geographical location where you can host your resources. Regions have three or more zones. For example, the us-west1 region denotes a region on the west coast of the United States that has three zones: us-west1-a, us-west1-b, and us-west1-c.
Zones Displays the total spend grouped by zones.
Labels
Displays the total spend grouped by labels that you added for your GCP resources.
Note: You can use labels to group resources that are related or associated with each other. For example, you can label resources intended for production, staging, or development separately, so you can easily search for resources that belong to each development stage when necessary. You always add labels as key and value pairs.
Projected Spend
The projected spend view provides insight into the actual and projected cost for the selected period. You can select different time ranges from the Time range drop-down list in the Filters option.
Table 2. Projected Spend
View Description
Overview Displays the projected and actual spend for the selected period.
Projects

Displays the projected and actual spend for all the projects in your GCP billing account.

Services Displays the projected and actual spend for all the services in your GCP billing account or project.
Compute
The Compute view provides the cost specific to all the compute resources configured on GCP. For example, Compute Engine, Cloud Dataflow, and so on.
Table 3. Compute
View Description
Overview Displays the total spend for all the compute resources for the selected period. You can hover over the graph to view the total spend for a specific day.
Projects Displays the total compute spend for all the linked projects in your GCP billing account.
Cost Centers Displays the total spend for all the compute resources grouped by cost centers.
Charge Types Displays the total spend for all the compute resources grouped by the GCP line item type.
Services Displays the total compute spend for all the services activated in the projects linked to the selected GCP billing account.
Usage Types Displays the total compute spend based on the usage types (OnDemand, Committed, and so on).
Regions Displays the total compute spend incurred across the GCP regions.
Zones Displays the total compute spend incurred across the GCP zones.
Labels Displays the total compute spend based on the labels applied to your GCP resources. You can click the Labels drop-down list to select a label.
Storage
The storage view provides the cost specific to your storage resources running on GCP. For example, Cloud Storage.
Table 4. Storage
View Description
Overview Displays the total spend for all your storage resources running on GCP for the selected period. You can hover over the graph to view the total spend for a specific day.
Projects Displays the total storage spend for all the linked projects in your GCP billing account.
Cost Centers Displays the total storage spend for all the resources grouped by cost centers.
Charge Types Displays the total storage spend for all the resources grouped by the GCP line item type.
Services Displays the total storage spend split for all the services activated in the projects linked to the selected GCP billing account.
Usage Types Displays the total storage spend based on the usage types (OnDemand, Committed, and so on).
Regions Displays the total storage spend incurred across the GCP regions.
Zones Displays the total storage spend incurred across the GCP zones.
Labels Displays the total storage spend based on the labels applied to your GCP storage resources. You can click the Labels drop-down list to select a label.
Network
The network view provides the cost specific to your networking resources running on GCP. For example, Cloud DNS, Virtual Private Network (VPN), and so on.
Table 5. Network
View Description
Overview Displays the total spend for all your network resources running on GCP for the selected period. You can hover over the graph to view the total spend for a specific day.
Projects Displays the total network spend for all the linked projects in your GCP billing account.
Cost Centers Displays the total network spend for all the network resources grouped by cost centers.
Charge Types Displays the total network spend for all the network resources grouped by the GCP line item type.
Services Displays the total network spend split for all the services activated in the projects linked to the selected GCP billing account.
Usage types Displays the total network spend based on the usage types (OnDemand, Committed, and so on).
Regions Displays the total network spend incurred according to the GCP regions.
Zones Displays the total network spend incurred according to the GCP zones.
Labels Displays the total network spend based on the labels applied to your GCP network resources. You can click the Labels drop-down list to select a label.

Cost Analytics (Multicloud)

The Analyze page allows you to track cost consumption across all your cloud resources (AWS, Azure, GCP, and Nutanix) at both the aggregate and granular level. You can drill down cost further based on the accounts, services, locations, or tags within your business unit or cost center.

Analyze

This view provides deep visibility into your projected and current spend. Analyze displays a line chart to project cost consumption that helps you view and analyze your cost and usage across all clouds, business unit, cost center, or scopes you select.

To view the Analyze page, click the Hamburger icon in the top-left corner to display the main menu. Then, click Analyze . Click View in the top-right corner to open the View Selector pop-up and select All Clouds .

Note: Currency toggle is not available for multicloud views. You can view the spend data in target currency on the multicloud dashboad. You can select the target currency in the currency configuration page. For more information on general guidelines and considerations, see Currency Configuration Considerations .
Current Spend
The current spend view provides the current costs across all configured clouds (AWS, Azure, GCP, and Nutanix) and its breakdown based on the different usage and resource data.
Table 1. Current Spend
View Description
Overview Displays the total spend across all configured clouds.
Accounts Displays the total cost of the linked accounts in your AWS payer account, subscription of your Azure account, and projects associated with your GCP billing account.
Cost Centers Displays the total spend grouped by cost centers across all configured clouds.
Services Displays the total spend grouped by services.
Regions Displays the total cost grouped by regions.
Tags Displays the total cost based on the service tag applied to your resources. You can click the tag drop-down list to select a service tag.
Projected Spend

The projected spend view provides insight into the actual and projected cost for the selected period. You can select different time ranges from the Time range drop-down list in the Filters option.

Filtering Options

The Analyze page allows you to track cloud spend across resources through various views—Current Spend, Projected Spend, Compute, and more. Clicking a view provides various group by selections to analyze in aggregation across accounts, services, regions, cost centers, and other different attributes. Each view also includes drill-down options to analyze granular information of that view.

In a view, you can drill down the cloud spend by clicking Filters . The Filters pane includes a set of fields that vary according to the cloud type. Select the desired resources to drill down your cloud spend and analyze only the resources of your interest. Further review the cloud spend analytics or download the reports specifically for these resources.

Figure. Analyze - Filters Click to enlarge

Time Period Type

You can select between Usage or Invoice to view the cloud spend analysis.
  • Usage . Beam uses the actual usage and the cost data incurred during the date range selected. Beam uses Usage to analyze spend-data by default.
  • Invoice . Beam uses the charges on invoices issued for months selected. When you select Invoice as the time period type, Beam uses Month as the time unit and disables the Day or Month selection.
Note:
  • For All Clouds , Financial , or Scopes view, you can select the Time Period Type filter only after you select the specific cloud—AWS, Azure, or GCP.
  • For AWS, the time period type depends on the AWS cost configuration.
    • Absolute Cost : The time period selection is configurable. You can either select Usage or Invoice .
    • Amortized Cost : The time period selection is Usage by default and the Invoice option is disabled.
  • The time period selection is not available for the following views.
    • Data Transfer for AWS
    • Projected Spend for all clouds
  • You can either apply Include or Exclude option to the resources selections in the filters.
  • You can do a keyword search to select the relevant resource from the drop-down list.
  • Your selections in filters are available across all group by in that view.

Anomaly Detection

The anomaly detection feature in Beam is an intuitive cost governance mechanism for public clouds (AWS and Azure).

Anomaly detection identifies and reports cost spikes in your cloud account by analyzing the spending trend on your subscribed resources.

You can use anomaly detection to discover cost anomalies and the resources that are causing the anomalies to take corrective actions, like, optimizing or shutting down resources that are not legitimate. Anomaly detection is useful for dynamic environments and where static budget thresholds are less efficient since they do not process the historical consumption pattern.

The cost anomalies are displayed in the timeline view of the Analyze page. Also, you can view the list of anomalies (if you have access to the AWS payer account or Azure billing account) as a separate widget in the Dashboard .
Note: AWS cost change reported in spend anomalies does not follow cost configuration and is based on unblended- and absolute-cost.

Viewing Cost Anomalies

Beam allows you to view anomalies detected in your AWS and Azure cost.

About this task

Anomaly detection identifies and reports cost spikes in your cloud account by analyzing the spending trend on your subscribed resources.

To view cost anomalies detected by Beam, do the following.

Procedure

  1. In the Beam console, click the View option in the top-right corner to open the View Selector pop-up and select the AWS or Azure account.
  2. Do one the following.
    • Go to the Analyze > Current Spend tab.

    • Go to the Dashboard and view the Spend Overview widget.

    Cost anomalies detected on your spending pattern are highlighted with an arrow sign pointing to the date on which the spike is detected. You can hover over the arrowhead icon to see the percentage increase in cost from the previous day.

    Figure. Viewing Cost Anomaly Click to enlarge anomaly detection

  3. Click the arrowhead hyperlink to go to the Anomaly Details dialog box to see the cloud accounts and resources that contributed to the spike. Anomaly Details shows anomaly details like date, resource name, and percentage increase in the cost from the previous date.
    Note:
    • Beam requires the complete cost data for a particular date to detect an anomaly. It may take up to 48 hours for the complete cost data from AWS and Azure.
    • An anomaly detected at a linked account- and subscription-level may not be bubbled up to the payer account- and billing account-level, respectively. This is because the anomaly detected at the linked account and subscription may be insignificant compared to anomalies at the payer account- and billing account-level, respectively.

Cost Reports

Beam generates reports to track cost consumption across all your cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications.

The reports are generated automatically and are available to view, download, or share from the Beam console. The daily, weekly, and monthly reports are also sent to the registered Beam administrator email address automatically. To customize your email notification preferences, select Profile from the user menu in the top right corner. Then, select Email Preferences in the Preferences section.

Note:
  • For Custom reports, the time period type is configurable. See Custom Reports.
  • For System reports, the time period type is usage by default.
  • The System reports are in target currency that is configured at the time of report generation. However, the following system reports are in source currency.
    Note: The following reports are in source currency.
    • Daily reports: New EC2 RI Recommendation report and EC2 RI Utilization Report
    • Monthly reports: Expired RI Report , Expiring RI Summary Report , and On Demand vs Reserved Hours Cost
  • The currency in the Custom reports is based on the configuration in the create or edit page. The reports are in either source currency or target currency as configured while creating the reports.
Table 1. Cost Reports
Report Description Clouds Supported
System Reports
Cost Report by Account Contains month to date detailed spend information based on accounts, regions, and services. The latest report is generated by the end of the day according to your timezone every day. AWS, Azure, and GCP
New EC2 RI Recommendation Report Contains instance-wise details such as region, platform, type, and reservation coverage. The latest report is generated by the end of the day, according to your timezone. AWS
EC2 RI Utilization Report Contains EC2 reservation planning information based on the instance type, region, platform with a complete aggregated account view. The latest report is generated by the end of the day, according to your timezone. AWS
Cost Optimization Detailed Report Contains detailed information about unused resources and rightsizing opportunities for the infrastructure of the selected account. The latest report is generated by the end of the day, according to your timezone. AWS, Azure
Tag Based EC2 Instance Type-wise cost Report Contains tag-wise cost separation, which will help you monitor spend based on resource tags. It also contains a spending breakdown based on the instance type. The latest report is generated by the end of the day, according to your timezone. AWS
Bandwidth Summary Report Contains transfer quantity in GB segregated by transfer type, account, service, resource, and region. The latest report is generated by the end of the day, according to your timezone. AWS
EC2 Detailed Insight Report Contains resource-wise cost optimization details like incurred cost, rightsizing, RI, recommended action, and other information. The latest report is generated by the end of the day, according to your timezone every day. AWS
Weekly Reports
Cost Report by Account Contains detailed spend information based on accounts, regions, and services for the last week. The latest report is generated by Tuesday of every week. AWS, Azure
Spend Report by Tags Contains spend information for the last week based on various resource tags for the selected account. The latest report is generated by Tuesday of every week. AWS
Cost Comparison Report Contains cost comparison data according to accounts, regions, and services for the past two weeks. The latest report is generated by Tuesday of every week. AWS
Monthly
Cost Report by Account Contains detailed spend information based on accounts, regions, and services for the last month. The latest report is generated by the 7th of every month. AWS, Azure, and Nutanix
Spend Report by Tags Contains spend information of last month based on various resource tags for the selected account. The latest report is generated by the 7th of every month. AWS
EC2 Spend Report Contains spend information based on the EC2 instance type, platform, accounts, regions, and purchase option for the last month. The latest report is generated by the 7th of every month. AWS
Cost Comparison Report Contains cost comparison data as per accounts, regions, and services for the last two months. The latest report is generated by the 7th of every month. AWS
Expired RI Report Contains information regarding the RIs that expired in the last 90 days. The latest report is generated by the 7th of every month. AWS
Expiring RI Summary Report Contains information about RIs expiring in less than 30 days, between 31 to 60 days, and between 61 to 90 days as well as their renewal cost. The latest report is generated by the 7th of every month. AWS
On Demand vs Reserved Hours Cost Contains a comparison between On-Demand and Reserved hours based on the instance type. The comparison also includes savings incurred on reserved hours for the last month. The latest report is generated by the 7th of every month. AWS

Guidelines for the Share , Schedule , and Download report options.

  • Share and Download options are available for all the views - Global view, Scopes, Business Unit, Cost Center, AWS (Overview, Payer, and Linked accounts), Azure (Billing Accounts and Subscription), and GCP (Overview and Billing accounts).
  • The Schedule option is available at the AWS, Azure, and GCP individual cloud level (Payer and Linked accounts, Billing Accounts and Subscription).

Scheduling Reports

Beam application generates reports to track cost consumption across all your cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications.

About this task

The application allows you to schedule reports at a desired time.

To schedule reports, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports .
    The System tab appears.
  2. Click View in the top-right corner to open the View Selector, and select the cloud account or Scope for which you want to schedule reports.
  3. Hover over any of the Daily , Weekly , or Monthly generated reports and click the schedule icon.
  4. Enter the Schedule Report Sharing details and click Schedule .
    All the schedule reports are available under the Reports > Scheduled Reports . You can edit, disable, or delete any scheduled report.

Downloading Reports

Beam application generates reports to track cost consumption across all your cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications.

About this task

The application allows you to download selected reports for offline consumption.

To download reports, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports .
    The System tab appears.
  2. Click View in the top-right corner to open the View Selector, and select the cloud account or Scope for which you want to download reports.
  3. Hover over any of the Daily , Weekly , or Monthly generated report and click the download icon.

Sharing Reports

Beam generates reports to track cost consumption across all your cloud accounts at both aggregate and granular levels, like a functional unit, workloads, and applications.

About this task

Beam allows you to share selected reports with stakeholders over email.

To share reports, do the following:

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports .
    The System tab appears.
  2. Click View in the top-right corner to open the View Selector, and select the cloud account or Scope for which you want to share reports.
  3. Hover over any of the Daily , Weekly , or Monthly generated reports and click the share icon.
  4. Enter the Recipients , Report Name , and Message .
  5. Click Share to complete.

Custom Reports

Custom reports help in strategic decision making and planning in the cloud. You can create a customized report by aggregating and filtering using various native cloud dimensions and attributes to get insights on cloud usage and cost. The Custom Reports page displays a list of all the custom reports created.

You can create a new report by clicking Add Custom Report at the top-right corner of the Reports > Custom . You can view, edit, schedule, share, download reports (CSV) or delete a previously created report by selecting the options next to the report name. To find a previously created report, start typing the report name in the search bar and select from the auto-populated options.

For more information, see Creating Custom Reports (AWS) and Creating Custom Reports (Azure).

Note:
  • A custom report can be created for AWS payer- and linked-accounts, Azure billing accounts and subscriptions.
  • To create a custom report, the user must have a Write access to the specified AWS payer- and linked-accounts, Azure billing accounts and subscriptions.
  • The saved reports are always available on the Beam console. For every custom report, a maximum of 100 entries gets displayed. To get the complete list of entries or offline consumption of the custom reports, you can download the custom report using the download icon.

Creating Custom Reports (AWS)

You can create a customized report to analyze the cost and usage across your AWS Accounts, Services, Region, and so on based on the defined range and filters.

About this task

To create a custom report, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu and then, click Reports .
  2. Click the Custom tab.
  3. Click View in the top-right corner to open the View Selector, and select the cloud account or Scope for which you want to create a custom report.
  4. Click Add Custom Report in the top-right corner.
    Figure. Custom Report Details Click to enlarge

  5. In Custom Report Name , enter a name for the report.
  6. In the Dimensions list, select a dimension for the required report output. Click Add Dimension if you want to select multiple dimensions.
    Note: A report must have at least one dimension. You can select up to ten dimensions.
  7. In Time area, you can select from the following options:
    1. In the Period Type list, click the drop-down list to select either Usage or Invoice type.
    2. In the Unit list, click the drop-down list to select either Day or Month to specify the time unit that you want to generate a report for.
      Note: The Invoice period type is only available for the Month time unit.
    3. In the Range list, click the drop-down list to select either date or month range based on the time unit selected. You can generate a custom report for the last 3 months.
  8. In Metrics area, you configure the following:
    1. Cost - After you select the Cost checkbox, the following the report cost presentation options appear.
      • A currency toggle. Select the currency with which you want to generate the custom reports. For more information, see Currency Configuration .
        Note: If the target currency is same as source currency, the toggle is not available.
      • Amortized Unblended
      • Absolute Blended
      • Absolute Unblended
      • Include Credit and Refunds
      • Include EDP Discounts
      Note:
      • The default selection is based on your AWS cost-logic configuration. For more information, see AWS Cost Configuration .
      • The Amortized Unblended option is only available when you select Usage as Period Type .
    2. Usage - Specify the usage quantity. By default, the Any filter is applied. You can use the drop-down list to apply the filter according to your requirement. The available options are Any , Greater Than Equal To , Less Than Equal To , and Range . The usage quantity unit corresponds to the selected service. For example, the usage unit is hours for EC2, bytes for S3, and so on.
    Note: Ensure that you select at least one of the following metrics - Amortized Unblended , Absolute Blended , Absolute Unblended , and Usage .
  9. To add more filters to your report, click Filters and do the following.
    1. In the Accounts list, select the accounts for which you want to generate a custom report.
    2. In the Service list, select the services from the available list.
    3. In Sub Service , select the sub-services you want.
    4. In Availability Zone list, select the availability zones you want.
    5. In API Operation list, select the API operations you want to include in the custom report.
    6. In Purchase Options list, select the purchase options you want.
    7. In Tag Key and Tag Value lists, select a key and value pair. Click Add another Tag Key Value Pair to add multiple keys and values.
  10. Click Generate .

Creating Custom Reports (Azure)

You can create a customized report to analyze the cost and usage across your Azure Subscriptions, Products, Region, and so on based on the defined range and filters.

About this task

To create a custom Azure report, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports .
  2. Click the Custom tab.
  3. Click View in the top-right corner to open the View Selector Pop-up , and select the cloud account or Scope for which you want to create a custom report.
  4. Click Add Custom Report in the top-right corner.
    Figure. Custom Report - Create Click to enlarge
  5. In Custom Report Name , enter a name for the report.
  6. In Dimensions , select the dimensions for the desired report output. Click Add Dimension if you want to select multiple dimensions.
    Note: A report must have at least one dimension. You can select up to 10 dimensions.
  7. In Time area, you can select from the following options:
    1. In the Period Type list, click the drop-down list to select either Usage or Invoice type.
    2. In the Unit list, click the drop-down list to select either Day or Month to specify the time unit that you want to generate a report for.
      Note: The Invoice period type is only available for the Month time unit.
    3. In the Range list, click the drop-down list to select either date or month range based on the time unit selected. You can generate a custom report for the last 3 months.
  8. In Metrics area, do the following to configure Cost .
    1. In the currency toggle, select the currency with which you want to generate the custom reports. For more information, see Currency Configuration.
    2. In the cost filter drop-down list, select the cost range by using one of the following logical operators.
      • Any . By default, the Any filter is applied.
      • Greater Than Equal To
      • Less Than Equal To
      • Range
  9. To add more filters to your report, click Filters and do the following:
    1. In the Subscriptions list, select the subscriptions for which you want to generate a custom report.
    2. In the Service Categories list, select the categories from the available list.
    3. In the Regions list, select the regions you want.
    4. In the Products list, select the products you want to include in your custom report.
    5. In the Cost Centers list, select the cost centers you want.
    6. In the Resource Groups list, select the resource groups from the available list.
    7. In the Departments list, select the departments you want.
    8. In Tag Key and Tag Value lists, select a key and value pair. Click Add another Tag Key Value Pair to add multiple keys and values.
  10. Click Generate . A preview of the report is displayed. You can click Save to save the report or click Edit to change the report parameters.

Report (Multicloud)

Beam generates reports to track cost consumption across all your cloud accounts at both aggregate and granular levels like a functional unit, workloads, and applications.

The reports are generated automatically and are available to view, download, or share from the Beam console. Beam sends the daily and yearly reports to the registered Beam administrator email address automatically.
Note: You can view daily reports only at the business unit and cost center levels.

To view the reports, click the Hamburger icon in the top-left corner to display the main menu. Then, click Reports . You can use the View Selector to select the business unit, cost center, or scope.

You can click the drop-down menu at the top-right corner to select the Daily Reports or Yearly Reports .

Table 1. Multicloud Cost Reports
Report Description
Cost Summary Reports Contains month to date detailed spend information based on accounts, regions, and services. Beam generates the latest report by the end of the day according to your timezone every day.
Cost Optimization Detailed Reports Contains detailed information about unused resources and rightsizing opportunities for the infrastructure of the selected business unit or cost center. Beam generates the latest report by the end of the day according to your timezone every day.
Historical Budget Reports Contains past financial year budget reports along with the quarterly summary data and service-wise cost breakdown for each quarter. Click View All to view the list of reports for the past financial years.

Chargeback

The Chargeback feature enables the financial control of your cloud spends by providing the ability to allocate cloud resources to departments based on definitions. Chargeback also provides a consolidated view across all your cloud accounts in a single pane of finance view.

Note:
  • Chargeback is built on the business unit and cost center configuration construct that you define for the resources across all your cloud accounts.
  • You cannot build chargeback on the custom scope. You define a scope using accounts and resources and can add a resource across different scopes.
  • For AWS, the time period type selection depends on the cost configuration.
    • If Absolute Cost type is selected, the time period type is invoice-based.
    • If Amortized Cost type is selected, the time period type is usage-based.
  • For Azure and GCP, the selection of time period type is invoice-based.
  • You can view the spend data in the configured target currency. For more information on general guidelines and considerations, see Currency Configuration Considerations .

Business Units

A business unit is defined as a collection of cost centers. You can use the business units to define hierarchies in your organization between different departments. It is not necessary to define a business unit to view chargeback. You can also define chargeback only based on cost centers.

Cost Center

A cost center is a collection of resources within a single or multiple cloud accounts (AWS, Azure, and GCP). You can assign the resources to the cost center based on tags. You can either allocate a complete account or resources within an account to a cost center.

Note:
  • If a cloud account is assigned to a cost center with the tag definition as All Tags , then you cannot share this account with another cost center.
  • An account or tag once used in a Cost Center definition cannot be reused. This is to prevent double-counting of the cost of resources.
  • The resources that do not belong to any of the cost centers are grouped under Unallocated Resources . You can manually allocate any unallocated AWS and Azure resources into a cost center. Beam does not support manual allocation of unallocated GCP resources.

Unallocated Resources

Unallocated resources are the resources that do not belong to any of the cost centers based on definitions.

Unallocated resources include the following.

  • Accounts not allocated to any cost center (includes all the resources within the account)
  • Resources within an account not allocated to any cost center.

The following image describes an example of a multicloud configuration. The cost center consists of Nutanix, AWS, Azure, and GCP resources.

Figure. Multicloud Configuration Click to enlarge

Adding a Business Unit

Before you begin

You can create a business unit only if you have an Admin role in Beam.

About this task

You can define a business unit by combining a group of cost centers. Chargeback is built on the business unit and cost center configuration construct that you define for the resources across all your cloud accounts. You can select the owners and viewers for the business unit. Both owners and viewers have read-only access to the business unit.

To add a business unit, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Chargeback .
  2. In the Business Unit Configuration page, click the Create list and select Business Unit .
    The Create Business Unit page appears.
  3. In the Name box, enter a name for the business unit.
  4. In the Owners list, click to select owners for the business unit you are creating.
    Note: The business unit owner is financially accountable for the business unit. You can select multiple owners for the business unit.
  5. In the Viewers list, click to select viewers for the business unit you are creating.
  6. In the Cost Centers list, select the cost centers that you want to map to your business unit.
  7. Click Save Business Unit to complete.
    The business unit you just created appears in the Business Unit Configuration page. You can use the business unit to build chargeback.

Editing a Business Unit

You can edit (or delete) an existing business unit.

Before you begin

You can edit or delete a business unit only if you have an Admin role in Beam.

About this task

To edit a business unit, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Chargeback .
    You can view the list of business units in the Business Unit configuration page. You can use the drop-down to filter the list by the business unit.
  2. Click Edit against the business unit that you want to edit.
    The Edit Business Unit page appears.
  3. Click Save Business Unit after you edit the fields according to your requirement.

Adding a Cost Center

Before you begin

You can create a cost center only if you have an Admin role in Beam.

About this task

A cost center is a department to which you can allocate cloud accounts and resources based on the definition. You can define a cost center by selecting resources by accounts and tags across different clouds. You can select the owners and viewers for the cost center. Both owners and viewers have read-only access to the cost center.

To add a cost center, do the following.

Procedure

  1. In the Beam console, click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Chargeback .
  2. In the Business Unit configuration page, click the Create list and select Cost Center .
    The Create Cost Center page appears.
  3. In the Name box, enter a name for the cost center.
  4. In the Owners list, click to select owners for the cost center you are creating.
    Note: The cost center owner is financially accountable for the cost center. You can select multiple owners for the cost center.
  5. In the Viewers list, click to select viewers for the cost center you are creating.
  6. Click Define Cost Center to open the Define Cost Center page.
    You define the cost center by selecting the accounts and tags across different clouds.
  7. In the Define Cost Center page, do the following.
    1. In the Cloud list, select the cloud type ( AWS , Azure , or GCP ).
    2. In the Parent Account list, select the parent account.
    3. In the Sub Accounts list, select the sub accounts. You can select multiple sub accounts.
    4. In the Tag Pair area, select the key and value pairs to further refine the definition of your cost center. You can click the plus icon to add more key and value pairs.
    5. Click Save Filter to save the filter. You can click Add Filter to add more filters.
    6. Click Save Definition to save your cost center definition and close the Define Cost Center page.
  8. Click Save Cost Center to complete.
    Beam takes around 24 to 48 hours to display the cost data of the newly added cost center.
    Note: If cost allocation tags for an AWS account are not visible in Beam, activate the cost allocation tags in AWS. To activate the cost allocation tags, see Activating the AWS-Generated Cost Allocation Tags.

Editing a Cost Center

Beam allows you to edit (or delete) an existing cost center.

Before you begin

You can edit a cost center only if you have an Admin role in Beam.

About this task

To edit a configured cost center, do the following.

Procedure

  1. Click the Hamburger icon in the top-left corner to display the main menu. Then, click Configure > Chargeback .
    You can view the list of cost centers in the Business Unit configuration page. You can use the drop-down list in the top-right corner to filter the list by the cost center.
  2. Click Edit against the cost center that you want to edit.
    The Edit Cost Center page appears.
  3. Click Save Cost Center after you edit the fields according to your requirement.
    Beam takes around 24 to 48 hours to display the cost data of the edited cost center.

Allocating Unallocated Resources To Cost Center

Before you begin

You can allocate an unallocated resource only if you have an Admin role in Beam.

Abou