Skip to main content

Admin Console

The Admin Console is the central workspace where administrators configure integrations for data ingestion and governance.

Who Uses the Admin Console​

The Admin Console is primarily used by Cloudaware administrators who are responsible for onboarding integrations, maintaining CMDB data quality, and managing access.

For a description of the administrator role and required permissions, see Cloudaware Administrators.

Access to the Admin Console​

To open the Admin Console:

  1. Log in to your Cloudaware account.
  2. Click the Hamburger menu (top‑left).
  3. Select Admin to open the console.

Admin Console Layout​

The Admin Console contains three navigation tabs in the sidebar:

  • CLOUDS & INTEGRATIONS
  • API CREDENTIALS
  • SUBSCRIPTIONS

Clouds & Integrations​

The CLOUDS & INTEGRATIONS section groups integrations and data sources into the following categories:

  • Cloud – Cloud providers, including AWS, Azure, GCP, Oracle Cloud, and Alibaba Cloud, as well as account-based integrations such as GitLab Accounts.
  • Billing – Cloud billing integrations and data sources, such as Kubernetes billing data collected through OpenCost.
  • DevOps – Engineering, infrastructure-as-code, and Cloudaware-managed services, such as Breeze and TunHub.
  • Container Infrastructure – Container platform data sources, such as Docker Registry.
  • Issue Management – ITSM and issue management tools, such as ServiceNow.
  • Logging – Log and event data sources, such as Splunk.
  • Monitoring – Observability and service health tools, such as AppDynamics and Datadog.
  • Security – Security, vulnerability management, and SIEM/SOAR systems.
  • Other – Identity-related systems, collaboration tools, and other integrations, such as Slack.

For available integration types and detailed setup guides, see Integrations.

API Credentials​

The API CREDENTIALS section allows users to generate OAuth Tokens and API Keys.

  • OAuth Tokens for External API access: Used to authenticate requests to the Cloudaware API. Each token is issued for a specific Cloudaware user, so API requests made with the token run on behalf of that user. The table here shows when each token was created, when it was last used, and its use count. Tokens remain valid until they are revoked and must be stored securely.
  • API Keys for MCP server connection: Used to connect supported AI clients to the Cloudaware MCP server. The table shows the key name, creation date, and expiration date. The API key is displayed only once after creation and cannot be retrieved later, so save it securely.

Subscriptions​

The SUBSCRIPTIONS section allows customers to save subscription codes for cloud provider marketplaces.

Using the Admin Console for Integrations​

  • To connect a new integration:
    • Find the integration in the list and click + ADD.
    • Complete the form, save, and validate the connection status.
  • To edit connection details or rotate credentials:
    • Find the integration in the list and click CONFIGURED.
    • Update the integration details and save.
    • Verify the integration status.
tip

When the integration is configured, a button IN NAVIGATOR appears on is pane in Admin Console. Click the button to open the tab and the panel in CMDB Navigator, showing objects related to this integration.

  • To remove the integration and related data:
    • Find the integration in the list and click CONFIGURED.
    • Find the relevant entry (account/data source/endpoint).
    • Open the three‑dot (⋮) menu and choose Delete.
    • After Cloudaware processes the deletion request, the integration and its data are deleted (retention periods for CI data in the CMDB may vary).

Relationship to CMDB UI and Navigation​

The Admin Console is about configuration, while the main CMDB UI is about usage:

  • Use the Admin Console to:
    • Connect and manage integrations and data sources.
    • Monitor the status of the enabled integrations.
    • Generate API credentials for External API and MCP server access.
    • Manage cloud marketplace subscription codes.
  • Use the CMDB UI (Navigator, Search, list views, CI detail pages) to:
    • Explore objects and relationships.
    • Run queries and reports.
    • Drive operations, investigations, and change workflows.

For an overview of how users navigate the CMDB, see UI & Navigation in CMDB and CMDB Navigator.

On this page