Cloud computing services for resource accounting establish, host, and manage services rented out to a remote consumer (individual or business). The scope of services ranges from offering essential computational assets like bandwidth, storage, and computational power to sophisticated enterprise applications such as SaaS.
The commonly used business model to charge for these services is a pay-per-use base, where the consumers use resources according to their needs and are then billed for the used resources at the end of a defined period. Idyllically, the consumers should be offered an explicit resource accounting model to identify all factors considered for calculating the consumption charges.
Giving the consumer access to their resource usage data can help them in IT budget planning, making aware billing applications, and automate the assortment of services according to their specific needs. Also, it is to the benefit of the cloud service provider to make this data available for consumers. It would help them come up with specifically designed user-centric services. Most providers already offer their clients their usage data. However, there are concerns regarding accountability.
An issue that concerns the resource accounting model for such services is the accountability of the resource usage data, whether it is the provider who does the measurements of this data, the consumer, or some other trusted third party.
A combination of these players to measure accountability is also an option. However, like other traditional utility services such as gas and electricity, provider-side accountability is the norm in the cloud services industry. But unlike the consumer-trusted metering for traditional utilities, there is no such metric for consumers to measure data usage. Therefore, they have no choice but to accept what the provider offers them.
Consumer side proposition
Continuing the above discussion, we propose a customer-centric resource accounting model to resolve the concerns of all parties. A customer-centric accounting model will allow the customer to calculate billing charges from the service provider programmatically. They will be obliged to respond to the request.
Subsequently, a customer-centric solid accounting model will measure the cloud services billing charges independently by the customer or a trusted third party. This will allow consumers to measure their billing charges, which is only fair. It is proposed that the providers adopt the customer-centric models to perform regular checks and raise alarms when there are apparent contradictions in the consumption data.
Inspecting consumer centricity of the resource accounting model
Many services providers provide or publish details of their billing information. However, it must be examined if the detailed information is by the customer-centric notion. We will start with a basic example and see if there is any room for any improvement.
To investigate the notion, we take a simple S3 cloud storage service from Amazon. It is an essential pay-per-use base service. It is marketed as a fast, reliable, and low-cost service yet, upon examination, researchers found few ambiguities in the model that cannot be programmatically queried from Amazon.
This suggests that even the simplest resource accounting models cannot match a robust consumer-centric model’s standards, relatively loosely coherent with the weak model. However, specifically for S3, the uncertainties can be fixed with ease internally by paying little attention. However, it is recommended that a cloud service provider opts for assembling the third party as a measurement service to access and measure their data usage efficiently.
One of the ambiguities was no reference to the time zone upon listing the price concerning geographical location. The start and end days of the billing cycle cannot be determined for sure. However, it can be inferred from the provided Amazon developers guide that S3 servers are synchronized to GMT.
Data and Metadata
Another concern of S3 is regarding the measurement of user data. In addition to its data, the S3 resource accounting model has system metadata and user metadata. System metadata is only used by S3, while user metadata is only used by the consumer and has a maximum size of 2KB. However, Amazon fails to clarify the actual storage space acquired by data and metadata.
Amazon states that they check the storage space consumed by the user at least twice every day. Though, they fail to mention the exact time these checkpoints take place. Upon further investigation, it has been observed that they do not check the cloud storage usage twice every day, and the event randomly takes place anytime in a Zulu time zone.
Therefore, it is concluded that the resource accounting model for the cloud still needs to define specific parameters of operation before they become trusted consumer utilities.About Complete Controller® – America’s Bookkeeping Experts Complete Controller is the Nation’s Leader in virtual bookkeeping, providing service to businesses and households alike. Utilizing Complete Controller’s technology, clients gain access to a cloud-hosted desktop where their entire team and tax accountant may access the QuickBooks™️ file, critical financial documents, and back-office tools in an efficient and secure environment. Complete Controller’s team of certified US-based accounting professionals provide bookkeeping, record storage, performance reporting, and controller services including training, cash-flow management, budgeting and forecasting, process and controls advisement, and bill-pay. With flat-rate service plans, Complete Controller is the most cost-effective expert accounting solution for business, family-office, trusts, and households of any size or complexity.