![]() |
Consumption Analytics Documentation |
This article details the credentials and permissions that you set up in your Amazon Web Services (AWS) accounts to give HPE Consumption Analytics Portal the ability to collect data and, in limited cases, make changes for you.
For each AWS user to whom you grant permissions, you must provide AWS credentials to HPE Consumption Analytics Portal.
The permissions in this section are needed for HPE Consumption Analytics Portal to collect detailed billing reports, which are the primary source of the data you see in HPE Consumption Analytics Portal reports and analytics.
The following permissions are required on the billing (payer) account for each AWS collection that you create. You cannot create a collection without them.
Because you enter the credentials for usage and billing data into HPE Consumption Analytics Portal separately from credentials for other access, you can use separate AWS user accounts for these two purposes.
The permissions in this section are needed for HPE Consumption Analytics Portal to collect resource utilization, application performance, and operational health data available through the Amazon CloudWatch service. This not only provides richer reporting, but also enables Insights to alert users to take action based on these metrics, such as when a resource is underutilized.
For each applicable account, the CloudWatchReadOnlyAccess policy is required. If this policy does not exist in your cloud, you must create a role with the CloudWatch Read Only policy.
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. Also, the account owner can limit the resources we are allowed to access if desired.
A sample policy is shown in the next section.
For the JSON version of the CloudWatch Read Only policy, see CloudWatch Read Only in the AWS documentation.
For general information about IAM roles, see Managing IAM Roles in the AWS documentation
(c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP