How to discover RDS instance running in AWS from service now

[jaganathant]

I can discover EC2 instances, load balaners , VPC etc. but I am unable to discover RDS instances running in AWS.

Is it possible to discover the RDS instances in Isthandbul and Helsinki ?

[scotnorthern]

While they are discoverable, if you previously had AWS Accounts set up and Discovery Schedules planned using those accounts, you must change them.  And, ServiceNow added a new place to look for these cloud service accounts which offer more options to see than under AWS Discovery. 

You now want to modify your Cloud Accounts under Cloud Management > Cloud Infrastructure > Service Accounts

First, You would need to add the AWS and cloud management capabilities to the MID server. You can do this by editing the Capabilities related list in the MID server form to add cloud management and AWS to the list. Also include ALL in the supported applications related list.

We had four AWS discovery schedules, which were deprecated in Jakarta (Discover type Web Service replaced by Cloud Resources).

We needed to delete the existing schedules and create new ones for each service account, by clicking on "Create Discovery Schedule" UI inside each of the cloud service account record.

Once we did that and Discovered the datacenters, we were able to see that the "Amazon AWS Relational Database Service" pattern would be launched to discover RDS instances

To recap:
1) Add those capabilities
2) Discover Datacenters
3) Create new AWS Discovery Schedules using the new Cloud Resources type
4) THEN run discover now

Also, when they are discovered, they come in under Database Instances with a class of Cloud Database

[Jace Benson]

I found your post really helpful @scotnorthern.

I made notes after I got this going on my instance;

1.  Create Classification Process for RDS.

2.  Associate the "Horizontal Pattern" with the Amazon Relational Databases pattern to it.

3.  Created new Amazon Web service with default endpoint of https://rds.amazonaws.com

4.  Created new related endpoint related to "Amazon Web service" mentioned in step 3. with appropriate regions.

5.  Create new Discovery schedule with type of cloud services.

6.  Added "All" capability to a mid server.

Also helpful about horizontal discovery was this video, but unrelated to aws discovery stuff.

https://www.youtube.com/watch?v=R_49vxeGz78

[Geet Rana]

Hi jacebenson,

Could you please elaborate steps which you have mentioned.

Like 1. Which Classifier type needs to be created and for which table and relation type(if needed). 

   also why do we need to add point 2 and 3 in this whole process.

Without creating the classifier won't it work.

also by adding  "All" capability to the mid server won't it affect other schedules using this mid server.

Thanks

[hiranmayeesahoo]

Do we need to install mid server on vpc to discover the AWS RDS instances or without mid server it works?

As it is horizontal discovery i think we need mid server

I am getting error "No process classification is defined for CI type" . Do we need to define custom process classification.

Can you please send sample of the same if possible

[Jace Benson]

The mid server is used to hit the aws endpoints, so no, it does not need to be on the vpc.