| copyright | lastupdated | keywords | subcollection | content-type | ||
|---|---|---|---|---|---|---|
|
2025-01-13 |
track-spend-with-cloudability |
faq |
{{site.data.keyword.attribute-definition-list}}
{: #ibm-cloud-enablement-faqs}
Review the FAQs for {{site.data.keyword.IBM_notm}} Cloudability Enablement deployable architecture. To view all FAQs for {{site.data.keyword.cloud}}, see the FAQ library. {: shortdesc}
{: #how-does-cloudability-access-my-billing-data} {: faq}
{{site.data.keyword.IBM_notm}} Cloudability accesses your account billing data by using billing exports to a Object Storage bucket. This deployable architecture creates the access policies to an {{site.data.keyword.IBM_notm}} Cloudability owned service ID to be able to read the data in this bucket. Only the bare minimum access is granted to {{site.data.keyword.IBM_notm}} Cloudability.
{: #how-long-until-I-see-my-data} {: faq}
Once the deployable architecture is deployed, your {{site.data.keyword.cloud_notm}} billing data should be imported into {{site.data.keyword.IBM_notm}} Cloudability within 24 hours.
Once my {{site.data.keyword.cloud_notm}} account is added to Cloudability, how many months of data is ingested into Cloudability?
{: #adding-historical-data} {: faq}
By default, the current month of {{site.data.keyword.cloud_notm}} billing reports is added to Cloudability. If additional months of data are needed, then open a support case with {{site.data.keyword.cloud_notm}} Billing to request that the historical cost data be sent to your billing reports Object Storage bucket. You can request up to 12 months of historical data. Once the files are in the bucket, contact the Cloudability Support team for your historical data to be ingested into Cloudability.
{: #why-no-immutable-storage}
No, immutable storage of objects is not a supported feature of billing exports to Object Storage. Billing exports updates a manifest file, which is what Cloudability reads. The updating of objects is not allowed when immutable storage is enabled.
{: #existing-object-storage-instance} {: faq}
Configure the deployable architecture to use an existing {{site.data.keyword.cos_short}} instance by entering the {{site.data.keyword.cos_full_notm}} CRN{: term} in the input field existing_cos_instance_id and set create_cos_instance to false. See the {{site.data.keyword.cos_short}} configuration reference for more details.
{: #existing-key-protect-instance} {: faq}
Yes, you can configure the deployable architecture to use an existing {{site.data.keyword.keymanagementserviceshort}} instance by entering the instance ID in the input field existing_kms_instance_guid and set create_key_protect_instance to false. To avoid a conflict, it may also be necessary to skip the creation of the authorization policy between {{site.data.keyword.keymanagementserviceshort}} and Object Storage if an authorization policy exists. To disable the creation of this authorization policy set the skip_iam_authorization_policy variable to true. See the configuration reference for more details.
{: #how-often} {: faq}
The billing reports are updated in the Object Storage bucket by {{site.data.keyword.cloud_notm}} Billing once a day. Cloudability fetches the data from the bucket in the same day.
{: #what-access-for-cloudability} {: faq}
Only the minimum required access is granted to Cloudability to access the billing data within the account. This access is controlled by using iam custom roles. The privileges granted to these custom roles include:
| Service Name | Permissions | Reason |
|---|---|---|
| {{site.data.keyword.cos_full_notm}} | * iam.policy.read \n * cloud-object-storage.object.head \n * cloud-object-storage.object.get_uploads \n * cloud-object-storage.object.get \n * cloud-object-storage.bucket.list_bucket_crn \n * cloud-object-storage.bucket.head \n * cloud-object-storage.bucket.get | To list the objects in the bucket and to read the contents of the billing report files. |
| {{site.data.keyword.IBM_notm}} Enterprise | * iam.policy.read \n * enterprise.account.retrieve \n * enterprise.account-group.retrieve | For enterprise accounts only. Needed for reading the names of the child accounts and account groups within the enterprise account. |
| {: caption="Cloudability access permissions" caption-side="bottom"} |
{: #cost-mismatch-prior-to-june-2024} {: faq}
There may be a discrepancy between your invoiced amount from {{site.data.keyword.cloud_notm}} and what appears in Cloudability for the data before June 2024. This discrepancy is because the tiered pricing amount on your invoice is for all instances in your account, whereas the amounts read by Cloudability did not share amounts between instances. This is because the data used by Cloudability is based on the resource instance usage file. This issue applies only to data added historically before the fix was applied on June 1st, 2024.
{: #cost-mismatch-invoice} {: faq}
The {{site.data.keyword.cloud_notm}} billing data that is used by Cloudability is from the usage reports, which may not reflect your invoiced amount. To learn more, see the tutorial, "how to reconcile usage and invoice files?" or visit the FAQ for invoices page to review the following topics:
Why does the cost for a past month in Cloudability not match a usage report that I recently downloaded?
{: #cost-mismatch-usage} {: faq}
Sometimes, the costs that are viewed in Cloudability for a previous month may not match a recently downloaded Resource Instance Usage report. The main reason for the mismatch is because usage for a service was submitted after the billing month closed. As an example, usage was submitted on the 1st of the month for the previous month. In this case, the billing report that is submitted to Cloudability for the last day of the month does not include this usage amount. However, a recently downloaded usage report for a past month includes the updated amount.
Why do my costs in Cloudability differ from the costs on the {{site.data.keyword.cloud_notm}} Usage page?
{: #cost-mismatch-ui} {: faq}
The primary reason that costs observed in Cloudability differ with the {{site.data.keyword.cloud_notm}} Usage page is because the {{site.data.keyword.cloud_notm}} Usage page is updated frequently with the latest usage information. Cloudability is only updated once a day and the amounts derive from the billing Resource Instance Usage report which are also updated less frequently than the {{site.data.keyword.cloud_notm}} Usage page