Cloud AWS Discovery is not completing

[kushal_dangare]

Hi

I am very new to implementing discovery. We are implementing Cloud AWS discovery.

I have configured the integration through IAM assume role (credential less discovery). I am able to validate the connection. However, the discovery is not completing. The Discovery status is still active after 1 day. There is no new update on logs or ECC queue. All the ECC queue are processed.

I have few more questions in general regarding AWS discovery:

1. Do we need to give IP ranges for the VM schedule generated through discovery manager wizard? Or are they suppose to come from first schedule of cloud resources. The VM schedule has not started since cloud resources is not complete.

2. Do we need to do anything on the firewall and server/instance credentials at this stage? Or these need to be configured when VM schedule is running? Do firewall and server/instance credentials required at all?

3. We are receiving few devices from cloud resource schedule. But they are all going into Cloud Resource class. Is it expected or are they suppose to go into various classes?

[PavanBV]

I have configured the integration through IAM assume the role (credential less discovery). I am able to validate the connection. However, the discovery is not complete. The Discovery status is still active after 1 day. There is no new update on logs or ECC queue. All the ECC queue are processed. ---> Could you please try restarting the MID Server/ Server itself and see if the discovery moves forward?

1. Do we need to give IP ranges for the VM schedule generated through the discovery manager wizard? Or are they supposed to come from the first schedule of cloud resources. The VM schedule has not started since cloud resources are not complete. --> Not needed, the IP details will come from the first schedule. If this isn't happening, you can also specify the IP Address/Subnets in the VM schedule explicitly and run it.

2. Do we need to do anything on the firewall and server/instance credentials at this stage? Or do these need to be configured when the VM schedule is running? Do firewall and server/instance credentials required at all? - If your requirement is to discover the CI's as well, not just the cloud resources, then all the pre-requisites like firewall, ports, credentials need to be in place as we generally do for on-prem discovery.

[Rahul Priyadars]

Crisply - Cloud Discovery has two things - Cloud Resource Discovery & Core Discovery .

Cloud Discovery will bring Cloud Resources like data center , cloud objects etc.

Now the next picture - Servers, VMs , etc are hosted in Cloud like AWS or Azure on which application, db etc runs.

You need to run Horizontal discovery (IP Range Scan) just like we do data center discovery to fetch Cis like Windows server, Linux Server, SQL Databases etc.

Regards

RP

[Prashanth Kuma4]

Can you check ECC Queue output status.

If it is ready, MID server didn't pick the output. It can happen if the MID server is in hung state or there are lots of records in queue which are in ready state. Restart the MID service and try. If it still doesn't work, you have to clear up your queue.

If it ecc queue output record is stuck in processing state, you need to enable debugging and check the MID server logs to find out which step it is taking more time to complete.

[kushal_dangare · Accepted solution]

Schedule got completed after we ran CPG to Pattern Migration