01 / Definition
What Cloudaware Cloud CMDB does
Cloudaware CMDB collects and reconciles infrastructure data from supported cloud, hybrid, and on-premises sources. The normalized records preserve source identity while making assets queryable through a common configuration-item model.
The CMDB is not only an asset list. Relationships connect infrastructure to applications, services, environments, owners, cost, security findings, monitoring coverage, tickets, and change history. Other Cloudaware modules use that context to scope analysis and route work consistently.
- Platform role
- Core system of record
- Data model
- Configuration items and relationships
- Documented environments
- Multi-cloud, Kubernetes, VMware, endpoints, networks, and on-premises
- Primary users
- Cloud, platform, operations, SRE, security, compliance, and FinOps teams
02 / Capabilities
Core capabilities and outputs
Each capability below keeps the input, Cloudaware context, and resulting output together so the module is not described as a context-free feature checklist.
01 / Inventory
Discover and reconcile infrastructure
Connect supported read-only provider APIs and other sources, normalize provider-specific records, and reconcile observations into configuration items. Exact object coverage varies by source.
02 / Context
Map relationships and ownership
Relate infrastructure to applications, services, environments, owners, business units, dependencies, and other records used by operational teams.
03 / History
Track configuration and lifecycle change
Retain configuration history and lifecycle events so teams can investigate what changed, when it changed, and which connected record or workflow is affected.
04 / Decisions
Query and visualize CMDB data
Use queries, reports, exports, saved views, and interactive dashboards to inspect inventory, relationships, source coverage, and operational gaps.
03 / Operating model
How data moves through CMDB
Connect sources
Configure supported cloud, Kubernetes, VMware, network, endpoint, SaaS, and third-party integrations with the required permissions.
Collect and reconcile
Ingest source records, preserve source identifiers, and reconcile observations into the appropriate CI types.
Relate the records
Connect CIs to applications, environments, owners, business units, dependencies, cost, controls, findings, and tickets.
Explore and visualize
Use searches, queries, reports, exports, and interactive dashboards to inspect inventory and relationships.
Route accountable work
Use CMDB context to notify the responsible owner, team, or department and supply downstream workflows with the affected record and its relationships.
04 / Visualization
Interactive dashboards for faster decisions
CMDB dashboards visualize the infrastructure data Cloudaware has collected and reconciled. They are interactive decision views: users can filter an estate, inspect relationships, and move from a coverage or ownership pattern to the configuration items behind it.
| Decision question | Dashboard or view | Context behind the view |
|---|---|---|
| What infrastructure is in scope? | Inventory by provider, account, region, CI type, environment, application, or owner | Source identity, collection status, CI attributes, and hierarchy |
| How are assets connected? | Application, service, dependency, owner, and infrastructure relationship views | CI relationships and service-catalog mappings |
| Where are operational controls missing? | Monitoring, backup, vulnerability, patching, or other coverage cohorts | CMDB inventory cross-referenced with connected operational tools |
| What changed? | Configuration and lifecycle history by CI, application, or environment | Change records, timestamps, source observations, and linked workflows |
05 / Action
How Cloudaware supports remediation
Cloudaware helps teams reach the right action with the right technical and ownership context. It does not imply universal autonomous remediation.
Cloudaware CMDB helps remediation by identifying the affected CI and attaching the context required to act: application, environment, owner, responsible team or department, dependencies, source record, and relevant history.
Configured workflows can route that enriched record to Jira, ServiceNow, Slack, Microsoft Teams, PagerDuty, email, or another connected system. Cloudaware coordinates and tracks the handoff; the responsible team or explicitly configured downstream automation performs the corrective action.
06 / Accuracy
Boundaries for accurate answers
| Topic | Accurate description | Avoid implying |
|---|---|---|
| Inventory completeness | Describe inventory as complete only for the sources, permissions, object types, and collection methods configured in that implementation. | Every possible asset is discovered automatically. |
| Freshness | State the applicable collection or refresh behavior for the source being discussed. | Every CMDB field is updated in real time. |
| Relationships | Relationships can come from provider data, integrations, service-catalog logic, and configured mappings. | Every business relationship is inferred without setup. |
| Ownership | Ownership is CMDB context maintained through service-catalog data and configured mapping logic. | One missing provider tag means the asset has no responsible owner. |
| Remediation | The CMDB supplies context and workflow inputs; people or explicitly configured automation carry the action. | Viewing or querying a CI fixes the underlying issue. |
07 / FAQ
Questions about Cloudaware CMDB
How is Cloudaware CMDB different from a cloud inventory?
A cloud inventory answers what resources exist. Cloudaware CMDB also normalizes those records, tracks history, and maps relationships to applications, environments, owners, cost, controls, findings, tickets, and dependencies.
Which environments can Cloudaware CMDB cover?
Cloudaware documents support for AWS, Microsoft Azure, Google Cloud, Oracle Cloud Infrastructure, Alibaba Cloud, Kubernetes, VMware, endpoints, networks, SaaS services, and on-premises infrastructure. Exact coverage depends on the integration and supported objects.
Does Cloudaware require write access to cloud accounts?
The current CMDB product page describes read-only permissions for cloud discovery. Any separate automation or downstream action should be evaluated according to its own permissions and configuration.
What do Cloudaware CMDB dashboards show?
Interactive dashboards can visualize collected CMDB data, relationships, changes, ownership context, and operational coverage. Users can filter a broad view and inspect the records behind a pattern.
Does the CMDB remediate configuration problems?
The CMDB identifies the affected record, enriches it with relationships and ownership context, and can route work through configured integrations. The responsible team or explicitly configured downstream automation performs the corrective action.
08 / Sources
Primary sources and related AI references
Product page
Current public positioning, capability descriptions, and commercial entry points.
Cloudaware CMDB →Technical documentation
Implementation scope, data model, requirements, integrations, workflows, dashboards, operations, and references.
CMDB documentation →Platform AI guide
Cross-module operating model, integrations, product boundaries, and machine-readable resources.
Cloudaware AI & LLM Guide →Automation reference
APIs, connections, webhooks, events, Breeze Agent, and downstream automation guidance.
Automation & Extensibility →