Unbale to set up pattern-based credentialless AWS Cloud Discovery

[marcguegueniat]

Hello,

I'm having trouble trying to configure Service Accounts for AWS Cloud Discovery.

I've created a new Service Account for AWS, but when I click on Discover Datacenters I get the following message:

Actually the message is true: we have migrated to Pattern Cloud Discovery

So I clicked on the "Discovery Scheduler" link as stated.
But I'm still stuck

It is saying that the Service Account is not active, I can't select it.

So I tried the "Add Account" option

But it won't let me enter the account id because it already exists

Any one knows the rigth way to set up this?

Some more informations:

- we are using credentialless AWS Discovery (I've set the mid.aws.instance_profile_name parameter on mid server)
- we have migrated CAPI to Pattern
- instance is on Utah patch 7
Regards,

[Mateus Oliveira]

Hi @marcguegueniat ,

Checking your screenshots, I can see that the error message when you tried to select the account says that the account is not Operational instead of not Active; Did you perhaps checked if the Operational Status of that account is not set as Operational by any chance? This could be preventing you from creating your Discovery Schedule.

Please, mark my response as helpful 👍 in case it helped you. Also, please mark the question as answered in case your issue is solved. This really helps future readers.

[marcguegueniat]

Actually the Service Account record was set to operational, strange.

I continued searching and I think the issue is that I submitted the Service Account before clicking on "Discover Datacenter".

Which prevent The discovery schedule UI from letting me create a new one.

I think the best way for me is to:

- create nothing via Service Account module (and delete what I've created)

- instead directly open url /$discovery_schedule_config.do

- refill in all the fields, with the option of "Add account"

nb: I've not fully tested this yet, because I have another issue on connectivity.

Regards,

[marcguegueniat]

Replying to myself, after a call with Now Support.

So the short answer is:

- do not click on discover datacenters when creating the service account

- instead, set install_status to 1 for the Service Account

- then you can use it in $discovery_schedule_config.do

note:

usefull KB : Member to Master Discovery using Accessor account - Support and Troubleshooting (servicenow.com)

Regards,