Nowadays, a majority of cloud service providers offer an API that allows users to interact with their infrastructure for the creation or deletion of resources, volumes, and images, to name a few. To use these APIs, users have to first authenticate using mechanisms based on key-password pairs.
However these mechanisms are quite cumbersome as users often have to search for their credentials on cloud provider websites or in their file systems. Besides, these key-password pairs are in the format of long and difficult chains of alphanumeric characters, which make them impossible or pretty difficult to remember. Even though the use of these key pairs is justified by security reasons, it clearly affects a user’s experience when having to access these APIs. In Cloud Application Manager, as well as in many other cloud platforms, users have to specify their credentials, in order to interact with cloud vendors such as AWS, Google Compute Engine (GCE), Microsoft Azure, VMware, Openstack or Cloudstack among others.
Our philosophy at Cloud Application Manager is to alleviate and minimize all tedious management operations which affect a user’s experience, as long as they don’t present security issues. In the following, we will focus on Google Compute Engine’s API which supports...