Skip to main content

Integrations

Connect cloud environments, billing sources, and third-party tools so Cloudaware can collect inventory, configuration, telemetry, security, operational, and cost data.

Use this section to find the right integration guide, prepare the required access, configure least-privilege permissions, and verify that Cloudaware is collecting the data as expected.

info

Audience: Cloudaware administrators, IT operations teams, security teams, DevOps teams, and FinOps users

What You Can Connect​

Cloudaware supports integrations for public cloud providers, VMware, cloud billing exports and cost APIs, ITSM and collaboration tools, monitoring platforms, security and vulnerability systems, identity providers, DevOps tools, data platforms, Kubernetes, endpoint management, webhooks, and platform utilities.

Most integration guides include:

  • Supported data sources and collection scope
  • Required permissions and prerequisites
  • Least-privilege access guidance
  • Setup steps
  • Verification checks
  • Troubleshooting guidance
  • Related Cloudaware objects and modules

Before You Start​

Before configuring an integration, make sure you have:

  • Administrative access to the Cloudaware account.
  • Access to the external account, tenant, project, subscription, tenancy, cluster, tool, or workspace you want to connect.
  • Permission to create or assign roles, policies, service accounts, service principals, API tokens, webhooks, OAuth clients, credentials, or integration users.
  • Required endpoint, organization, project, tenant, billing scope, storage, dataset, bucket, report, or API details.
  • A clear understanding of the integration scope, such as a single cloud account, cloud organization, billing account, Kubernetes cluster, or third-party tool instance.
  • Network access between Cloudaware and the external system, where applicable.

Choose an Integration​

Start with the system you want Cloudaware to collect data from or send data to.

Cloud Providers and Infrastructure​

Connect cloud accounts, virtualization platforms, Kubernetes environments, and network discovery sources so Cloudaware can collect infrastructure inventory, relationships, and configuration data in the CMDB.

Billing and Cost Data​

Billing integrations map cost and usage data to discovered resources. Configure the matching cloud or infrastructure integration first, then add the billing source, such as AWS Billing, Azure Billing, Google Billing, Oracle Billing, or Kubernetes Billing via OpenCost.

Identity, Directory, and PAM​

Use integrations such as Active Directory (LDAP), CyberArk, Google Workspace (G Suite), and Okta Organizations to connect identity, directory, and privileged access context to Cloudaware. These integrations help teams understand ownership, access relationships, organizational structure, and authentication dependencies for CMDB assets.

Data Platforms​

Use integrations such as MongoDB Atlas and Snowflake to add inventory and configuration context from data platforms to Cloudaware. These integrations help teams include managed databases and analytics platforms in CMDB views, ownership models, and operational reporting.

Security and Vulnerability Management​

Use integrations such as Carbon Black Cloud, Cloudflare, CrowdStrike, Orca Security, Qualys, and Rapid7 InsightVM to enrich Cloudaware CMDB records with security findings, vulnerability data, endpoint signals, and threat context. Connect SIEM/SOAR integrations, Sophos, Tanium, Tenable Security Center, Tenable Vulnerability Management, and Trend Micro Deep Security to help security and operations teams prioritize remediation using ownership, environment, and resource context already collected by Cloudaware.

Endpoint and Device Management​

Use integrations such as Jamf and SCCM to bring workstation, server, and endpoint inventory into Cloudaware. These integrations help teams connect device management data with CMDB assets, ownership, compliance, and operational workflows.

Monitoring and Observability​

Use integrations such as AppDynamics, Datadog, Dynatrace, Nagios, New Relic, and Pingdom Account to bring monitoring signals and service health context into Cloudaware. Connect Sensu, SolarWinds, Splunk, Wormly, and Zabbix to help teams correlate infrastructure inventory in the CMDB with alerts, performance data, and availability checks from observability tools.

Log Management​

Use integrations such as AlienVault OTX and Conflux to send operational, cloud, and threat intelligence logs to Cloudaware Log Management. These integrations help security and operations teams centralize log ingestion, search activity across connected systems, and investigate events in Cloudaware's Conflux.

DevOps, SDLC, and AppSec​

Use integrations such as Ansible, Chef Ohai, Checkmarx One, GitHub, and GitLab to connect engineering systems, infrastructure-as-code tools, and application security findings to Cloudaware. Connect Heroku, Snyk, and Terraform to help teams relate cloud and CMDB assets to repositories, deployment workflows, automation, and software risk.

ITSM, Collaboration, and Notifications​

Use integrations such as AlertOps, Amazon SNS, Jira, PagerDuty, ServiceNow ITSM with ServiceNow Notification, and Slack to bring Cloudaware asset, incident, and operational context into the tools teams use to manage work. Leverage Slack Notification, PagerDuty Notification, and Rally Notification integrations to create tickets, route alerts, synchronize CMDB records, and keep responders informed without switching between systems. The Cloudaware CMDB Application for ServiceNow, a ServiceNow app, helps ServiceNow admins and ITSM teams with sync Cloudaware CMDB data into ServiceNow and keep CI records aligned.

Webhooks, APIs, and Connectivity​

Use Pingdom Webhook, Sumo Logic Webhook, and other integrations, to exchange data with Cloudaware through APIs and webhooks. Explore APIs & Connections and Webhooks & Events to learn more about how teams can automate workflows, receive external events, and send Cloudaware updates to other tools. Breeze Agent and TunHub are Cloudaware-managed integrations for collecting data from private environments and establishing secure access when direct connectivity is not available.

Typical Integration Workflow​

  1. Review the integration guide and confirm prerequisites, supported scope, endpoint requirements, and authentication method.
  2. Prepare the external system by creating the required role, policy, service account, token, webhook, application, export, report, bucket, dataset, or endpoint.
  3. Configure least-privilege access for Cloudaware.
  4. Add the integration in Cloudaware using the required account, tenant, project, billing source, workspace, or instance details.
  5. Test or verify the connection.
  6. Confirm that the expected resources, costs, tickets, events, records, assets, or telemetry appear in Cloudaware or the connected external system.
  7. Use the guide's troubleshooting section to resolve permission errors, missing data, connectivity failures, export delays, rate limits, or data mapping issues.