Highlighted
Micro Focus Expert
Micro Focus Expert
645 views

(UCMDB) SUPPORT TIP - AWS discovery problems

Issue:

Discovery has failed with the below error:

<<Progress message, Severity: Error>>

Failed to run Amazon Cloud discovery

<<Progress message, Severity: Warning>>

awsprotocol: Connection failed.

However, able to login from the UCMDB directly – what is causing the problem?

Solution:

The probe will do the actual discovery and maybe one need to configure the proxy settings if this is the only way to access AWS

Suggested workaround to get the AWS discovery successful when there is proxy involved.

Provide the proxy directly with the AWS credentials (right click and select “Edit Using Previous Interface”) -> clear probe results cache -> Rerun the discovery and we should get AWS discovery successful.

 

MICRO FOCUS Software Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Please hit the Kudo botton, if you find this post useful.
Labels (1)
Tags (1)
0 Likes
5 Replies
Highlighted
Regular Contributor.
Regular Contributor.

Re: (UCMDB) Support Tip - AWS discovery problems

Hi,

i am using UCMDB 10.32 cp 23.
I am also getting similar error for aws discovery.

It is giving error as "missing aws sdk jar file exception"
I have placed the aws sdk to discovery probe under ../content/lib/aws

Thanks in advance
Priyanka
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: (UCMDB) Support Tip - AWS discovery problems

I attached the set-up that I have.
0 Likes
Highlighted
Regular Contributor.
Regular Contributor.

Re: (UCMDB) Support Tip - AWS discovery problems

i have copied same jar files to probes
0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: (UCMDB) Support Tip - AWS discovery problems

I am facing the same issue, did you find any workaround?
0 Likes
Highlighted
New Member.

Re: (UCMDB) Support Tip - AWS discovery problems

Hi,

I have worked with application team regarding this issue and they have provided the proper permission for the user.

Thanks

Priyanka

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.