Skip to main content

CMDB Requirements

To get full value from Cloudaware CMDB, make sure your environment meets the baseline requirements below before enabling large‑scale ingestion.

Prerequisites​

  • Cloudaware account and cloud integrations.
    Connect your primary cloud providers (AWS, Microsoft Azure, Google Cloud, Oracle Cloud, or Alibaba Cloud) using read‑only roles or service principals. Use the guides in Integrations for provider‑specific prerequisites, least‑privilege policies, setup steps, and supported services.

  • On‑prem and data center inventory.
    Where applicable, integrate VMware vCenter and other on‑prem inventory sources so servers, virtual machines, and network devices appear alongside cloud resources in CMDB.

  • Breeze Agent coverage.
    Deploy Breeze Agent to servers and Kubernetes nodes where OS‑level data (packages, services, users, mount points, configuration files, etc.) is required. Breeze also enables security modules like IDS, Vulnerability Management, and Patch Management that rely on CMDB.

  • Third‑party integrations.
    Configure billing, monitoring, security, and ticketing tools so their data is ingested and attached to CMDB configuration items (CIs). See Integrations for integration‑specific requirements.

  • Identity, access, and least privilege.
    Use dedicated, read‑only identities for each integration with clearly scoped permissions. Follow provider guides to avoid write or admin privileges unless explicitly required.

  • Network access.
    Allow outbound TLS (HTTPS) connections from Cloudaware collectors and Breeze Agents to the relevant provider APIs and Cloudaware endpoints the agents need to call. No inbound connectivity to your environment is required.

  • Tagging and metadata conventions.
    Adopt consistent tagging/labeling for ownership, application, environment, and criticality so CMDB can drive accurate reporting, scoping, and automation.

Scale and Operational Considerations​

  • Environment size.
    CMDB can track large numbers of CIs (instances, containers, databases, storage, network objects, applications, etc.) across many accounts and regions. Start with a subset of accounts, validate data quality, then scale ingestion gradually.

  • Collection schedules.
    Data discovery and refresh jobs in Cloudaware run on provider-specific intervals, ranging from 5 minutes to 24 hours, to balance data freshness with API rate limits. High‑change environments may require more frequent collection for specific resource types.

  • Data retention and history.
    Plan for historical change tracking and growth in CI and relationship counts over time. Coordinate with your Cloudaware representative if you expect unusually large environments or have extended retention requirements.

  • Operational monitoring.
    Ensure the teams responsible for cloud integrations monitor ingestion health, alerts, and logs. Define a process for responding to permission errors, API throttling, and failed collections.