AWS Discovery : Discovers only Data Base

Amit Sharma4
Mega Expert

Hi There

I recently started discovering our AWS cloud. We applied IAM policy which is attached here.

After the discovery, i can see only the Databases in the discovered data center (only 1 data center shows these DB resources) and it does not discover any other resources like VMs, Availability Zone, Hardware type etc.

Discovery logs shows:

No Route53 Hosted Zone is found, Pattern name: Amazon AWS Route53 and No RDS is found in the LDC (region), Pattern name: Amazon AWS Relational Database Service,  message for the other data center for which discovery did not find any thing.

and ecc queue shows only Amazon AWS Relational Database Service and  Amazon AWS Route53  as the launched patterns.

I wonder if the data center is all empty other than those DBs or i am doing some mistake some where with the access.

 

Please advise.

 

Thanks

Amit

1 ACCEPTED SOLUTION

Amit Sharma4
Mega Expert

What i know so far is , at times during the upgrade (before jakarta) in some of the instances the CMDb parenting changes from CMDB to CMDB CI table and that cause a break in code.

This is known to servicenow but i am not sure if they have specifically said that it is fixed in X version.

A better  way will be to create a HI ticket, get it investigated from them/

 

View solution in original post

9 REPLIES 9

Saketh
ServiceNow Employee
ServiceNow Employee

Goto cmdb table. See if you can find the logical datacenters here. If you can find them, it could be a different issue.

If you cannot, it's a table reparenting issue.  A PRB will soon be opened for the reparenting issue.

Hi Saket, 

 

Got a confirmation from SNOW that it is CMDB Re-Parenting issue,

Thanks for your response. 

 

i'll post if i get more on it.

 

Thanks

Amit

hiranmayeesahoo
Kilo Expert

Is there any particular version they are fixing the issue?

I am also facing the issue "No RDS is found in the LDC (region), Pattern name: Amazon AWS Relational Database Service" for all regions

Amit Sharma4
Mega Expert

No, it seems CMDB re-parenting issue is not version specific. I would say, you create a ticket with them and push for an enhancement request.

Amit Sharma4
Mega Expert

What i know so far is , at times during the upgrade (before jakarta) in some of the instances the CMDb parenting changes from CMDB to CMDB CI table and that cause a break in code.

This is known to servicenow but i am not sure if they have specifically said that it is fixed in X version.

A better  way will be to create a HI ticket, get it investigated from them/