Skip to content
This repository has been archived by the owner. It is now read-only.
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Version Note, 2021-1-27

If you're ready to move off of the long-since obsolete Python 2 App Engine, Iris3 is now available. Iris3 not only modernizes your infrastructure, but adds many features and fixes many bugs. See the README for details.

Blog Post

In Greek mythology, Iris (/ˈaɪrɪs/; Greek: Ἶρις) is the personification of the rainbow and messenger of the gods. Iris was mostly the handmaiden to Hera.

Iris helps to automatically assign labels to Google Cloud resources for better manageability and billing reporting. Each resource in Google Cloud will get an automatically generated label in a form of [iris_name:name], [iris_region:region] and finally [iris_zone:zone]. For example if you have a Google Compute Engine instance named nginx, Iris will automatically label this instance with [iris_name:nginx], [iris_region:us-central1] and [iris_zone:us-central1-a].

Iris will also label short lived Google Compute Engine instances such as preemtible instances or instances managed by Instance Group Manager by listening to Stackdriver Logs and putting required labels on-demand.

NOTE: Iris will try tagging resources in all project across your GCP organization. Not just the project it will be deployed into.

Supported Google Cloud Products

Iris is extensible through plugins and new Google Cloud products may be supported via simply adding a plugin. Right now, there are plugins for the following products:

  • Google Compute Engine (including disks and snapshots)
  • Google Cloud Storage
  • Google BigQuery
  • Google Bigtable


We recommend to deploy Iris in a separate project within your Google Cloud organization. To deploy, you will need to have Owner role on Iris project and the following roles in your GCP Organization:

  • Organization Role Administrator - to create a custom IAM role for Iris that allows setting labels on the services (note this is different from Organization Administrator, which is in turn not related to Organization-level Owner)
  • Security Admin OR Organization Administrator - to allow Iris app engine service account to use the above role
  • Logs Configuration Writer OR Logs Configuration Writer - to configure log events stream on Organization level to watch for new instances, databases, etc.

Install dependencies

pip2.7 install -r requirements.txt -t lib

Yes, we still use Python2.7. Yes, we know.


./ <project-id>


Configuration is stored in the config.json file. The file contains two arrays.

  1. tags - A list of tags that will be applied to the resources (if the corresponding plugin implemented a function _get_<TAGNAME>())
  2. on_demand - A List of plugins that will tag whenever a new object of their type is created
  "tags": [
  "on_demand": [

Local Development

For local development run: --log_level=debug app.yaml

Iris is easily extendable to support tagging of other GCP services. You will need to create a Python file in the /plugin directory with register_signals, def api_name and methodsNames functions as following:

     def register_signals(self):

          Register with the plugin manager.

        logging.debug("BigQuery class created and registering signals")
 def api_name(self):
        return ""
	// a list of log methods to listen on
    def methodsNames(self):
        return ["storage.buckets.create"]

All plugins are derived form Plugin class and needs to implement the following functions:

  1. do_tag(self, project_id)
  2. get_gcp_object(self, data)
  3. tag_one(self, gcp_object, project_id)
  4. api_name(self)
  5. methodsNames(self)

Each plugin will execute gen_labels() which will loop over all the tags that are defined in the config file and will execute _get_<TAGNAME>() function


Automatically tag Google Cloud resources for better manageability and billing reporting





No releases published


No packages published