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.
