Skip to main content

CMDB Ingestion

CMDB ingestion discovers, imports, and refreshes configuration data from cloud providers, on-premises environments, Breeze Agent, billing integrations, and third-party tools.

This section explains how to connect sources, control schedules, and keep data healthy.

Cloud Provider Connections and Permissions​

Connect AWS, Microsoft Azure, Google Cloud, Oracle Cloud, Alibaba Cloud, and VMware vCenter with read‑only identities. For each provider:

  • Configure roles, service principals, or API keys with least‑privilege permissions.
  • Select the accounts, subscriptions, projects, and regions that should be in scope for CMDB.
  • Verify that initial discovery completes and that core resource types, such as compute, storage, networking, databases, security, and identity resources, appear as configuration items (CIs) in CMDB.

Additional Sources (Breeze, Billing, Third‑Party Tools)​

Beyond cloud control planes, CMDB ingestion also pulls data from:

  • Breeze Agent for OS‑level facts and runtime telemetry. See Breeze Agent for deployment and configuration requirements.
  • Cloud billing integrations that enrich CMDB objects with cost and usage context. See the billing-specific guides in cloud integrations.
  • Monitoring, ticketing, and security platforms documented in Integrations, which associate alerts, incidents, vulnerabilities, and other signals with CMDB CIs.

Make sure these sources are connected before relying on CMDB for coverage and gap analysis across security, cost, and monitoring.

Discovery Schedules and Throttling​

Each integration runs on one or more schedules that determine how often Cloudaware calls provider APIs or external systems. When designing schedules, Cloudaware:

  • Starts with recommended provider defaults, then tunes schedules based on your environment’s rate of change.
  • Refreshes high-churn resources, such as instances, containers, and autoscaling groups, more frequently.
  • Refreshes slower-changing resources, such as VPCs, subnets, and IAM roles, less frequently.
  • Respects API rate limits for each provider by adjusting concurrency or frequency when throttling errors appear in ingestion logs.

Data Freshness and Health Checks​

HHealthy CMDB ingestion means that object counts, relationships, and timestamps reflect the current environment within an acceptable delay. The following best practices are recommended:

  • Monitor last successful collection time and object counts per integration, account, and region.
  • Use CMDB queries and dashboards to spot stale areas (for example, resources not updated in several days).
  • Regularly review coverage for critical resource types to ensure new accounts, regions, and services are onboarded as your environment grows.

Troubleshooting Ingestion Failures​

When data appears missing or out of date:

  • Check the status of the relevant integration and review any error messages or recent changes (credentials, permissions, scopes).
  • Confirm that required IAM roles, service principals, or API keys still exist, are not expired, and have the permissions described in the provider guides.
  • Verify outbound network connectivity from Cloudaware collectors and Breeze Agents to cloud APIs and Cloudaware endpoints.
  • Look for API throttling or quota errors and adjust schedules or scopes if needed.
  • If issues persist, collect integration identifiers and recent error details before contacting Cloudaware Support at support@cloudaware.com for assistance.