It's the CMDB your Jira issues point to. Each incident, change or request concerns one or more CIs. Many Jira Service Management teams use Jira Assets for this. With Cloudaware, the CMDB lives in Cloudaware and updates itself through discovery. Jira issues link to its CIs.

Jira CMDB

Put the right CI on every Jira issue

Q: What does Cloudaware discover?

Cloudaware discovers every resource in AWS, Azure, Google Cloud, Oracle Cloud, Alibaba Cloud and Kubernetes. It finds virtual machines and hosts in VMware vCenter and Nutanix. It finds network devices through SNMP or SolarWinds. It finds laptops and phones through Microsoft Entra ID, Jamf and SCCM. It also lists the software installed on each machine.

Q: Does Cloudaware replace Jira Assets?

No. Your team keeps working in Jira. Jira Assets still suits a curated set, such as business services and long-lived servers. Cloudaware holds the full discovered inventory and puts the right CI on each issue. On request, it can also load a filtered set into Jira Assets.

Q: How does a CI get onto a Jira issue?

Two ways. Your team can pick it in the Cloudaware CI field by name, instance ID or IP address. Or the Cloudaware linker finds those identifiers in the issue and links the CI for them.

Q: Does the CI field use Jira Assets objects?

No. The CI stays in Cloudaware, and the issue links to it. Your Jira Assets object count doesn't change.

Q: Which Jira deployments does Cloudaware support?

Cloudaware reads issues from Jira Cloud and Jira Server through an API token. A Jira Server on a private network connects through TunHub. The CI field is an app for Jira Cloud.

Q: What does the linker add to an issue?

A comment from the Cloudaware CMDB app. It links each matched CI and lists its application, environment and owner. It links only identifiers that match a CI. You choose which projects it watches and which fields it fills.

Q: Can Cloudaware open Jira issues?

Yes. A Cloudaware Workflow opens an issue when a CI or a policy finding meets your condition. As the CI changes, the workflow comments on the issue. Jira Automation can then move or close it.

Q: How does the price compare with Jira Assets?

Cloudaware lists at $0.008 per CI per month. Jira Assets lists at $0.02 per object per month above the plan allowance. Premium includes 50,000 objects, and Enterprise includes 500,000. Both are list prices, before volume discounts.

Q: How long does setup take?

Cloud and SaaS sources connect with an API key. Data center discovery runs from one virtual appliance on your network. Most teams reach a production-ready setup in 30 to 45 days.

Cloudaware discovers your cloud, data center and devices with no manual entry. Your team picks the CI in Jira, or Cloudaware links it for them.

Works in Jira Cloud

Searches by name, ID or IP

Uses no Jira Assets objects

Shows issues on each CI

Jira's Create issue screen. The Cloudaware CI field lists three matches for breeze from the Cloudaware CMDB.

Work in Jira with the CI on every issue

Pick the CI in Jira

Search the Cloudaware CMDB from the issue screen. Find a CI by name, instance ID or IP address.

Link issues automatically

Alerts and emails often name an instance or an IP address. Cloudaware finds it and links the matching CI.

See the owner on the issue

Cloudaware adds the CI's application, environment and owner. The person working the issue knows who owns it.

Skip the Jira Assets import

Cloudaware discovers your resources and tracks every change. Nothing is copied into Jira Assets.

Teams that run their CMDB on Cloudaware

Discovery

What Cloudaware discovers

Cloudaware connects to your clouds, data centers, devices and tools through their APIs. Nobody types in a CI. Every CI stays current as things change.

Cloud

Every resource type in every account, from virtual machines to keys and queues.

AWS
Azure
Google Cloud
Oracle Cloud
Alibaba Cloud
Kubernetes

Data center

Virtual machines, hosts, datastores and bare-metal servers.

VMware vCenter
Nutanix
SCCM

Network

Switches, routers and other devices on your network. Cloudaware scans with SNMP, or reads a source you already trust.

SNMP discovery
IP discovery
SolarWinds

End-user devices

Laptops, phones and tablets, matched to the people who use them. Add purchase records to track warranty and end of life.

Microsoft Entra ID
Jamf
SCCM
Cloudaware agent

Software

Installed software and versions on every server and laptop. Cloudaware flags software that isn't on your approved list.

Endpoint tools
Cloudaware agent

Security and monitoring coverage

Cloudaware matches your security and monitoring data to each CI. You see which machines nobody scans or monitors.

CrowdStrike
Qualys
Tenable
Rapid7
Datadog
New Relic
Dynatrace

Cloudaware checks each source against the others. A host your security tool sees but your inventory doesn't is flagged.
Devices with no purchase record are flagged too.
Every change is kept, including resources that no longer exist. You can see what a CI looked like last week.

See all 100+ integrations

How Cloudaware connects Jira issues and CIs

CI field

Choose the CI when you create the issue

The Cloudaware app adds a CI field to Jira. Type a name, instance ID or IP address, then pick the match. The issue links to that CI in Cloudaware. Nothing is copied into Jira Assets.

Search by name, instance ID or IP address
Open the CI in Cloudaware from the issue
Works in Jira Cloud

A Jira incident, 502 Bad Gateway on breeze-os-updater, with the Cloudaware CI field set to breeze-os-updater-proxy: an AWS EC2 instance in the Breeze account, us-east-1, environment production, running.

Linker

Link issues that come from alerts and email

These issues often name an instance ID, IP address or host name. The Cloudaware linker reads each new or updated issue. It links every CI it finds and adds the application, environment and owner. Its comments come from the Cloudaware CMDB app, not from a person's account.

Links only identifiers that match a CI
Takes application, environment and owner from the service catalog
Lets you choose the projects and fields

A Jira task created from a monitoring email names an instance ID. The Cloudaware CMDB app comments with the matching CI, breeze-facts-sender-pg, and its application Breeze Patch Delivery, environment production and owner platform-team.

In Cloudaware

See every issue on the CI

Cloudaware imports Jira issues and matches each one to its CIs. Open a CI to see its issues next to its changes and dependencies.

Connects to Jira Cloud or Jira Server with an API token
Reaches a private Jira Server through TunHub
Reads every project its Jira account can see

The Cloudaware record of breeze-os-updater-proxy, application Breeze OS Updater, environment production, owner platform-team, with its Jira issues tab listing an open 502 incident and a to-do on the health check.

Workflows

Open Jira issues from Cloudaware

Set a condition in a Cloudaware Workflow. When a CI meets it, Cloudaware opens a Jira issue in the project you choose. When the CI is fixed, Cloudaware comments on the same issue. Jira Automation can then close it.

Fills the project, issue type and summary from the CI
Posts updates as comments on the same issue
Leaves status changes to Jira Automation

A Cloudaware workflow for production EC2 instances with an empty owner tag creates the Jira task No owner: breeze-nat, then comments on it when the owner tag is set to platform-team.

Issue keys and issue text are examples. CI, application and owner names come from the Cloudaware demo environment.

AI agents that work in Jira and Confluence

Cloudaware's AI-based products read the CMDB and the service graph through Cloudaware's hosted MCP. They know each CI's application, owner and dependencies. They post their work where your teams already look.

SRE Assist in Jira

Get an investigation on every linked incident

When an incident is linked to its CI, SRE Assist investigates. It checks recent changes, the request path and the CI's dependencies. It posts what it found and the next steps on the issue. It changes nothing.

Reads the CMDB and the service graph
Posts findings on the Jira issue
Read-only

A Jira incident, 502 Bad Gateway on breeze-os-updater. SRE Assist comments with the cause, two clean checks, a warning about an expired certificate and the next step.

Live docs in Confluence

Keep every DR runbook current in Confluence

An agent writes each application's DR runbook from the CMDB. It lists the resources, the order to restore them and what blocks recovery. It rewrites the page on your schedule, such as every morning. The same agent can write architecture pages with diagrams.

Recovery order from real dependencies
Blockers listed first
A new version on every run

A Confluence page, Breeze platform: DR runbook, updated today at 06:00. It shows 5 blockers and a five-step restore order from network to traffic.

Application hub in Confluence

Give each application owner one page

Agents assess each application for resiliency, security, compliance, cost and modernization. The results land on one Confluence page per application. The owner works from one ranked list instead of separate requests from each team. Findings from your other tools can land there too.

One page per application
One ranked list per owner
Updated from the CMDB

A Confluence page for the Breeze platform application with five assessments, their status and headline, and the owner's ranked list.

Issue keys, page names and findings are examples. CI and application names come from the Cloudaware demo environment.

See the CI field and the linker live

Book a one-hour demo with a solutions engineer and a technical account manager. We build it around your team's Jira use cases and run it on a Cloudaware demo environment.

Mikhail Malamud
General Manager

Jira Assets and the cloud

Jira Assets works best with a curated set

Business services, accounts, long-lived servers and network devices fit it well. Cloud resources change all day. Instances start and stop, and settings change on resources nobody tracks as CIs. A copy in Jira Assets falls behind unless someone curates it. Loading it also runs into Atlassian's limits.

Capacity

Atlassian allows 3 million objects per site by default. You can request up to 10 million. Atlassian tests your site first, and you pay for the larger tier.

Price

Objects above your plan's allowance cost $0.02 each per month at list price. Premium includes 50,000 objects. Enterprise includes 500,000.

Loading

The Assets API creates one object per call. Most endpoints allow 1,000 calls a minute. At that rate, 3 million objects take about 50 hours to load.

Need some CIs in Jira Assets too? Cloudaware can load a filtered set on request. We don't recommend loading everything. See how the Cloudaware CMDB discovers resources

Cloudaware costs $0.008 per CI per month

Monthly list prices, before volume discounts. Jira Assets charges only for objects above the plan allowance. Jira Service Management agent licenses are not included.

CIs held

Jira Assets Premium 50,000 objects included

Jira Assets Enterprise 500,000 objects included

Cloudaware $0.008 per CI held

Price per month per object or CI

$0.02 above the allowance

$0.008

3 million CIs Atlassian's default limit per site

$59,000

$50,000

$24,000

10 million CIs Available from Atlassian on request

$199,000

$190,000

$80,000

Jira Assets: objects above the allowance × $0.02. For example, 3 million objects on Premium is 2.95 million above the allowance. Cloudaware: CIs × $0.008.

Sources: Atlassian Assets licensing, Atlassian Assets pricing update, 10 million objects in Assets

Jira CMDB FAQ

What is a Jira CMDB?

What does Cloudaware discover?

Does Cloudaware replace Jira Assets?

How does a CI get onto a Jira issue?

Does the CI field use Jira Assets objects?

Which Jira deployments does Cloudaware support?

What does the linker add to an issue?

Can Cloudaware open Jira issues?

How does the price compare with Jira Assets?

How long does setup take?

Do the AI agents change my infrastructure?

Can I use my own AI assistant?

What else can run on a linked issue?

Try Cloudaware with Jira

One hour with a solutions engineer and a technical account manager
Built around your team's Jira use cases
Run on a Cloudaware demo environment