AWS Cloud VM instance not getting Discovered

[Abhishek41]

Hi All,

we were getting some VM instance discovered previously but suddenly we stopped seeing them . When I tried debugging the Amazon -AWS host LP pattern logs I am seeing the error saying " Host is empty Failed Condition(s): [(${all_hosts} : value=[]) IS NOT EMPTY ]" . Do you know why we are getting for the cloud vm instance discovery ?

I also tried to run the Amazon -AWS Virtual server pattern but unable to run the debug as after adding the required parameters such as object ID  etc still it is not running.

Any inputs will be appriciated. 

Thanks,

Abby

Abhishek

[Oyvind Schei]

Hi Abby!

The error message you're encountering, "Host is empty Failed Condition(s): [(${all_hosts} : value=[]) IS NOT EMPTY]", suggests that the discovery process is not finding any VM instances to report. This can happen due to a variety of reasons. Here are some common areas to check and potential solutions:

1. AWS Permissions: Ensure that the account used for discovery has the necessary permissions to list and access the VM instances. If permissions were changed or the role was modified, it could lead to an inability to discover instances.
2. Discovery Configuration: Verify that the discovery configuration is correct. This includes checking the region, network settings, and any filters that may be limiting the scope of the discovery.
3. Network Issues: Sometimes network configurations or changes can prevent discovery tools from accessing the AWS environment. Ensure that there are no network issues or firewalls blocking the discovery process.
4. Changes in AWS Environment: If there were recent changes in the AWS environment, such as moving instances to a different region, VPC, or subnet, these changes might affect discovery.
5. Discovery Tool or Pattern Version: Ensure that you are using the latest version of the discovery tool or pattern. Sometimes, older versions might not be compatible with the current AWS configurations or might contain bugs.
6. Amazon -AWS Virtual Server Pattern Configuration: Since you mentioned issues with running the debug after adding the required parameters, double-check the configuration and parameters. Make sure that the Object ID and other required fields are correctly filled in and valid.
7. Logs and Error Messages: Examine other logs and error messages closely. Sometimes they can provide more context or point to a specific issue that is not immediately obvious.
8. Resource Limits: Check if there are any resource limits in your AWS account that are being hit. For example, API rate limits or EC2 instance limits.
9. API Connectivity: Verify that the discovery tool can successfully make API calls to AWS services. Any issues with API connectivity could lead to a failure in discovering instances.

If these checks don’t resolve the issue, you may want to reach out to AWS support for more detailed assistance, as they can provide insights specific to your account and its configurations.

Hope this could lead to a solution! 🙂

[Abhishek41]

Thanks. Do you know where the API fail logs will be registered in servicenow for  AWS discovery as I checked the pattern/ecc queue/disocvery/Cloud trail logs but I did not find anything related to it. 

Thanks,

Abby

[Oyvind Schei]

As we all know, logs are spread all over the instance, I would look for logs in the following places:

1. ECC Queue

2. Discovery Log

3. Cloud Management Logs

4. System Log

5. Script Log

6. MID Server Log

7. AWS CloudTrail
   
   Hope it helps Abby 🙂