AWS RDS Discovery - CI Name populated with DBName instead of DBInstanceIdentifier
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2026 03:14 AM
Hello Community,
We have observed that AWS RDS Discovery populates the CI Name field with the database name (DBName), such as salones or initial, instead of the AWS RDS Instance Identifier (DBInstanceIdentifier), such as renault-rds1-prod or renault-rds1-staging.'
PROD CI -
STAGING CI -
From our investigation, this appears to be standard out-of-the-box behavior. However, in our CMDB, using the RDS Instance Identifier would provide better visibility and uniqueness, as multiple RDS instances can share the same database name.
Questions:
- Has anyone else encountered this challenge with AWS RDS Discovery?
- Do you use the default behavior (DBName) or have you changed the CI Name to use the AWS RDS Identifier?
- If customized, did you implement it through a Pattern Extension, Business Rule, or another supported approach?
- Have you experienced any upgrade or maintenance challenges after implementing the customization?
We're interested in understanding how other organizations manage AWS RDS CI naming and whether there is broader interest in having the RDS Instance Identifier used as the default CI Name.
Thank you in advance for sharing your experiences and recommendations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @PrasadShelar ,
I have experience in CMDB and Discovery, but not with this specific AWS RDS Discovery.,
My suggestion towards the 3rd and 4th step would be ..
- Extend the AWS RDS discovery pattern. Don’t edit the original pattern.
- Add a step that sets the CI name to the instance identifier.
- Keep the database name in another field so you don’t lose it.
- This is the supported way to customize patterns, and it usually survives upgrades better than editing the base pattern.
- One thing to not before doing this modification make sure the rule for this class doesn’t use the name to match records. If it does, a name change could create duplicate CIs.
Hope this helps, If it is useful please mark it as helpful and please Accept My Solution..
Best Regards
SIVASANKARI S