Skip to main content

Google Cloud Verification

Use this checklist to confirm that your GCP integration is healthy and that Cloudaware is ingesting the expected data.

Check Service Account and Project Status in Cloudaware​

In Cloudaware, go to Admin:

  1. Open Google Cloud PLatform → CONFIGURED.
  2. On the Service Accounts tab:
    • Confirm that the added service account shows a green status indicator.
    • Yellow or red status indicates missing access to the organization or that the account may have been removed in GCP.
  3. On the Projects tab:
    • Confirm that the GCP projects you expect to monitor are discovered and have a healthy status.
    • Review lifecycle state versus Cloudaware status for any warnings or access errors.

If many projects show denied or unreachable statuses, review IAM roles and service account assignments.

Validate Sample Resources in CMDB​

In Cloudaware CMDB Navigator:

  • Navigate to GOOGLE CLOUD PLATFORM → COMPUTE → Google GCE instances.
    • Confirm that a representative set of instances from onboarded projects appears.
    • Verify key fields such as project, zone, machine type, instance status, and labels.
  • Navigate to STORAGE, NETWORKING & CONTENT DELIVERY, DATABASE, and any other categories relevant to your environment.
    • Spot‑check that new or recently changed resources in the GCP console appear in Cloudaware after the next discovery run.
  • If you enabled GKE, billing, or SCC, check the corresponding categories for clusters, billing objects, and security findings.

Confirm Freshness of Data​

For selected objects (for example, a GCE instance or Cloud Storage bucket):

  • Check the Created By timestamp in Cloudaware (for initial setup).

    tip

    Allow initial collection latency for as little as 5 minutes or as long as 24 hours, depending on scope, connector scheduling, and platform load.

  • Check the Last Modified By timestamp to compare with the time of your most recent changes in Google Cloud. Prefer resources where a known recent change occurred (e.g., tag update, resize, configuration change) to view updates in the CMDB within the expected processing window.

    note

    Last Modified By in Cloudaware can’t be treated as a freshness SLA for static or rarely changing resources.

If timestamps are stale across many objects, there may be an integration or scheduling issue.

Validate Reporting Behavior​

Once inventory looks correct:

  • Open the CMDB list view for the relevant resource type and confirm that the default list views organize resources as expected, including populated columns for name, resource ID, and any available telemetry or cost data.
  • Open cost, security, or operational dashboards that include Google Cloud data and verify that counts and totals are reasonable.

When to Contact Support​

Contact Cloudaware Support with screenshots and example resource IDs if:

  • A service account remains red or yellow after you have confirmed IAM roles and API enablement.
  • Specific services (for example, GKE, billing, or SCC) remain empty despite correct permissions.
  • Data appears significantly delayed or inconsistent across regions or projects.