Amazon ElastiCache and RDS are not getting updated in Cloud Databases table

[Community Alums]

Hello All,

I have observed that all ElastiCache instances and not RDS database instances are not getting updated although Cloud related discovery schedules are running updating other cloud resources.

I have cross checked with AWS team and found that these ElastiCache instances and not RDS database instances are exists in cloud however ENI (IP's) associated with these CI's are eighter changed or not exists

Currently, For the RDS instances, it appears that the ServiceNow Discovery process does not handle IP/ENI (Elastic Network Interface) changes, gracefully.  AWS automatically changes the underlying IP address of RDS instances for various reasons and not have control this process.

When I checked ElastiCache and RDS related Horizonthal Discovery logs for one particular datacenter found some warnings (PFA  Screenshot for the same Cloud database -1,2,3 for ElastiCache  and RDS -1,2)

[RamakrishnaA]

Updating the thread just in case someone needs this fix.

Refer to Azure resources not discovered through Cloud Discovery - Support and Troubleshooting

Resolution

Follow the instructions in the Microsoft Azure resource inventory discovery documentation (see Related Links).

Specifically, add the following resource type to the sa_cloud_inventory_resource_whitelist allow list table if the resource type is not already present:

1. Cloud Vendor = Azure
2. Resource Type = Appropriate Azure Resource Type

See the mapping for Azure Resource Type in the Microsoft Learn: Azure Resource Graph table and resource type reference (see Related Links).

Run the Discovery Schedule. When the schedule completes, the resources will be visible in Cloud Resources [cmdb_ci_cmp_resource]. 

If a Custom Discovery Pattern is preferred, that is possible. Custom Discovery Patterns fall outside the base system functionality, and support options may be limited — check with ServiceNow Support for guidance.