IaaS cloud computing services for libraries: Cloud storage and virtual machines

Purpose: The purpose of this article is to provide an overview of current uses of cloud computing (CC) services in libraries, address a gap identified in integrating cloud storage in IaaS level, and show how to use EC2 tools for easy backup and resource monitoring. Design/methodology/approach: The article begins a literature review of CC uses in libraries, organized at the SaaS, PaaS and IaaS levels. The author presents his experience of integrating cloud storage services S3 and GCS. In addition, he also shows how to use virtual machine EC2 tools for backup and monitoring resources. Findings: The article describes a case study of integrating cloud storage using S3 and GCS. S3 can be integrated with any program whether the program runs on cloud or locally, while GCS is only good for applications running on GAE. The limitation of the current GCS approach makes it hard to use for a stand-alone cloud storage. The author also discusses virtual machines using EC2 and its related tools for backup, increase storage, and monitoring service. These services make system administration easier as compared to the traditional approach. Research limitations/implications: The article presents current CC uses in libraries at the SaaS, PaaS, and IaaS levels. CC services are changing quickly. For example, Google has stated that its APIs are experimental. Readers should be aware of this. Practical implications: The author shows his experience of integrating cloud storage services. Readers can understand the similarities and differences between S3 and GCS. In addition, readers can learn the advantages and concerns associated with implementing cloud computing. Readers are encouraged to consider questions such as content, skills, costs, and security. Originality/value: There are many uses of CC services in libraries. However, gaps are identified: in IaaS cloud storage, a few libraries used Amazon S3 and Microsoft Azure, but none explored using Google Cloud Storage (GCS); none provided implementation details, difficulties, and comparisons of S3 and GCS; and a few articles have briefly discussed implementations on Amazon EC2, but have not provided specific details about upgrade and backup. This article addresses those gaps. © Emerald Group Publishing Limited.