![]() |
Consumption Analytics Documentation |
HPE Consumption Analytics Portal retrieves Amazon Web Services (AWS) consumption data using the AWS Billing API. This not only provides richer reporting in HPE Consumption Analytics Portal, but also enables Insights that alert you to take action based on these metrics.
HPE Consumption Analytics Portal does not support AWS accounts in India that are operated by Amazon Internet Services Pvt. Ltd (AISPL), a local reseller in India. To determine which company your account is with, refer to the AWS documentation.
HPE Consumption Analytics Portal reads metrics for the following namespaces:
If you're using Amazon CloudWatch, HPE Consumption Analytics Portal can collect performance and utilization data through the CloudWatch API. Because HPE Consumption Analytics Portal collects data nightly, it collects unblended rates, which are more accurate on a day-to-day basis than blended rates.
Every night, HPE Consumption Analytics Portal collects usage, billing, and performance data from one or more of your Amazon web Service (AWS) accounts. If you have linked accounts, HPE Consumption Analytics Portal collects usage and billing data from the payer account, and CloudWatch performance data from each of your linked accounts. During this nightly collection HPE Consumption Analytics Portal collects data for the current and previous months. This ensures that if something in your AWS bill changes, you always have the most current data available in your HPE Consumption Analytics Portal analytics.
HPE Consumption Analytics Portal also collects tax information from the AWS bill, where those records appear with the description Tax of type <type>. In HPE Consumption Analytics Portal, this description appears in the Product field. The Resource ID for these records begins with the prefix Tax-. If the tax is a monthly charge, it appears in HPE Consumption Analytics Portal with the usage for the last day of the month.
For more information about how HPE Consumption Analytics Portal maps cloud providers' source data to HPE Consumption Analytics Portal normalized fields, see Field mapping.
Before you can create an AWS collection, you must set up the AWS account to work with HPE Consumption Analytics Portal. How you need to set it up depends on the type of credentials you want to use, and the data source from which you want the HPE Consumption Analytics Portal to collect your data.
As you set up your AWS account(s) in AWS, note the items in bold in this section - you'll need them later when creating an AWS collection in HPE Consumption Analytics Portal.
The step-by-step instructions in this section explain how to set up your AWS data collection with access key and secret.
These steps do not apply to data collections using delegated access, so if you plan to use delegated access credentials, you can skip to the next section and set up your data source.
If you create your HPE Consumption Analytics Portal AWS data collection using key and secret credentials, then all linked accounts will also use key and secret credentials. If you create the data collection using delegated access credentials, then all linked accounts within will also use delegated access credentials.
The authentication method can be changed in the future if necessary. In this case, it will be necessary to change your AWS account setup and collection configuration in HPE Consumption Analytics Portal accordingly.
To use key and secret credentials
This role provides a mechanism to allow a third party to access your AWS resources without needing to share long-term credentials. You need to give this role the appropriate permissions to allow HPE Consumption Analytics Portal to discover the linked accounts within the AWS account and access it to collect usage information.
For further details on permissions requirements, including sample policies, see AWS permissions needed by the HPE Consumption Analytics Portal.
The resources HPE Consumption Analytics Portal attempts to read are the ARNs that appear in the billing reports that support CloudWatch metrics. The tool only needs access to metrics, not logs; the only request executed is GetMetricStatistics. Also, the account owner can limit the resources we are allowed to access if desired (see AWS permissions needed by the HPE Consumption Analytics Portal).
When you create an AWS data collection in HPE Consumption Analytics Portal, you have the option to collect data from either the AWS Detailed Billing Reports (DBR) or the AWS Cost and Usage Report (CUR). Either way, you must set up your data source in AWS before you can create your data collection in the HPE Consumption Analytics Portal.
The Detailed Billing Reports feature in AWS is deprecated in favor of the Cost and Usage Report. It is unavailable for new AWS customers as of July 2019.
To collect data from an AWS Cost and Usage Report
Create a Cost and Usage report in AWS for the account for which you want to collect data, by following the instructions in Creating Cost and Usage Reports in the AWS documentation.
To enable your HPE Consumption Analytics Portal collection:
To collect data from AWS Detailed Billing Reports
Turn on the legacy Detailed Billing Reports in AWS for the account for which you want to collect data (see the instructions in Understand Your Usage with Detailed Billing Reports in the AWS documentation).
If you are using consolidated billing, perform this step for the payer account, not the linked accounts. For more information about consolidated billing, see Pay Bills for Multiple Accounts with Consolidated Billing in the AWS documentation.
To enable your HPE Consumption Analytics Portal collection:
Once you've set up your AWS account for the credentials and data source you want theHPE Consumption Analytics Portal to use, continue with the steps in the next section to create your AWS collection.
If you intend to create a collection with delegated access credentials, keep your AWS session open, because there are a few more steps to do in AWS as you create the collection in HPE Consumption Analytics Portal.
When you create an AWS data collection in HPE Consumption Analytics Portal, you have the option to create it (and all linked accounts in the collection) with Access Key ID and Secret Key authentication, or with Delegated Access authentication. The step-by-step instructions that follow show you how to create an AWS data collection in the HPE Consumption Analytics Portal with either access key and secret or delegated access.
To create an AWS collection
If you enter invalid credentials, you will see the following message:
In this case, correct the error and try again.
The instructions on the right hand side of the screen will update based on which radio buttons you select for AWS authentication and reports.
You can copy the external ID manually, or use the copy button to the right of the field.
You need the external ID, along with the AWS account ID for the HPE Consumption Analytics Portal, to create the Amazon Resource Name (ARN) in your AWS account (the ARN is needed to create your collection if you configure it to collect metrics as well as cost and usage).
For the AWS account ID, please contact HPE Support using the Contact Support link in the bottom right corner of this screen.
The resources HPE Consumption Analytics Portal attempts to read are the ARNs that appear in the billing reports that support CloudWatch metrics. The tool only needs access to metrics, not logs; the only request executed is GetMetricStatistics. Also, the account owner can limit the resources we are allowed to access if desired (see AWS permissions needed by the HPE Consumption Analytics Portal).
If there are multiple accounts to be ignored, you can simply skip entering credentials (step 12) in those rows. When you click Next, in step 13, the following warning will display at the bottom of the screen, and you can ignore all of them in one step by clicking Ignore all accounts without valid credentials.
For a list of the specific HPE Consumption Analytics Portal metrics collected from AWS and other providers, see Performance and utilization metrics.
If you notice a gap in your AWS performance data in HPE Consumption Analytics Portal charts and reports, you might have reached the CloudWatch API limit. Enter an AWS Support case to have your limit increased.
Amazon implements limits on customer accounts to prevent runaway usage, including a monthly limit of 1 million CloudWatch API requests. (For information about this and other CloudWatch limits, see CloudWatch, CloudWatch Events, and CloudWatch Logs Limits in the AWS documentation.) The more AWS resources you are using, the more CloudWatch API requests are needed to collect metrics data for those resources. Unfortunately, the limit does not scale with the number of resources you have in production, and it is possible to reach the limit with fewer than 300 AWS resources. If you reach the limit, HPE Consumption Analytics Portal can no longer collect CloudWatch data.
You must have a Developer, Business, or Enterprise support plan with AWS to submit a technical support case. If you have the Basic plan, you cannot submit a technical support case.
To request an AWS rate increase
To speed a resolution with AWS Support, include your AWS region as part of your request.
(c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP