What’s New in 18.5

Newly Added Support


In our first pass at support for Kubernetes, we’ve included support for Nodes, Pods, Containers, Services, Ingresses, Deployments, and Node mapping to cloud instances.

Expansion of Google Cloud Platform

Release 18.5 is heavily focused on Google Cloud Platform. We have added API visibility, support for GKE (Google Kubernetes Engine), Directory (Users/Groups), IAM (Roles, Service Accounts), Dataproc, Spanner, VPC Network Peers, BigTable, and FileStore.

Cloud Summary and Status

Harvest status and resource visibility status are now broken into separate columns to avoid confusion. Harvest Status is now isolated to three values: Running, Paused, Impaired. Resource visibility is now viewed in the Visibility column. If there are invalid/missing permissions affecting resource visibility, affected resources are noted in a pop-up.

Additionally, we’ve included a way to disable resource types from being harvested. This functionality has been added for those customers that have resources they don’t need or have permission to see. For example, a highly regulated company may have governance policies in place that may not give visibility to DivvyCloud for specific resources. Or, for AWS customers without an AWS Premium Support Subscription, AWS blocks the API from collecting information regarding Trusted Advisor. In both cases, disabling harvesting on those resources allows customers to harvest only relevant resources and eliminate visibility warnings.

Previous 18.4 Cloud Status View:

New 18.5 Cloud Status View:

Under the Clouds section of the tool, there is now a Summary tab that surfaces information about Child Cloud Accounts if the Parent Cloud Account is connected to DivvyCloud. When the Parent Cloud Account is connected, the Summary tab will populate the Cloud Account Coverage table, which lists Child Cloud Accounts and indicates whether they are also connected to DivvyCloud. This is useful for showing blind spots of cloud accounts that aren’t being monitored through DivvyCloud.

Below the Cloud Account Coverage table, there is a new section that shows Instance Counts per Cloud Account. Simply click on the cloud account in question and the graph will show Compute, Database, Big Data, Cache and Elasticsearch Instances along with Volumes and Storage Containers. This can be helpful when trying to view counts of large billable resources in specific accounts.

The last section of the Summary tab shows Cloud Provider Count. This graph will break down how many accounts you have from different cloud providers.

Resource View

In 18.5, we realized that we’ve added so much Resource support, that when a user clicks on a resource type, they may miss the resource information rendered on the bottom half of the page. To improve resource listing visibility, we introduced a tabular view for resources types, keeping them grouped by Compute, Storage, Network, Identity & Management, and adding Kubernetes.

Previous 18.4 Resource View:

New 18.5 Resource View:

In addition to the new tabular view, we’ve also included the ability to view tags while browsing in the resources section. By clicking on the tag shaped button on the top left, users can input the tags they’d like to view in the table below.

Tag Explorer Updates

In 18.4, we introduced Tag Explorer. Tag Explorer allows customers to audit and identify resources that contain (or do not contain) one or more tag keys. It supports many of the popular resource types used today across compute, storage (with the exception of snapshots), networking and identity management. With 18.5, users can now save their tag configurations for future use or to share with other users in their organization.

The previous Tag Explorer page has been reworked into a detail view with the “Saved Configurations” page serving as the starting point.

Enhancements to System

To help Domain Administrators, we’ve surfaced more operational data and capabilities in the System Administration section of the tool. Specifically, Domain Administrators now have the ability to see whether there are Assume Role failures for AWS accounts and inspect which accounts are affected.

Domain Administrators can also force a refresh of their license if there is an expiration.