With cloud CIs coming into play, the periodic discovery and update of CDMB is further challenged because of the considerations outlined below. In many cases, this was an acceptable tradeoff. At times, this could lead to stale inventory data because the CMDB update was not in real time. These attributes were updated per the periodic discovery cycle. The CMDB data is represented as a point-in-time snapshot of the configuration item (CI) record covering the resource attributes, ownership, relationship to other Cis, and major lifecycle timestamps like creation, decommissioned dates, and so on. Enterprises have relied on CMDB solutions either as part of their ITSM suite or as a standalone product (COTS or custom Microsoft Excel based inventory) to support ITIL processes and change, configuration, and incident management. We will talk about where to track the CIs, which items to track, how to track them, and tagging strategies for simplified tracking.
We are going to review some common needs when building a CMDB and the relevant AWS services that will help you build a comprehensive solution.
In this post, we will show you how you can design and implement a configuration management database (CMDB) strategy as part of your cloud operating model.
0 kommentar(er)
