AWS Discovery Schedule - To Enable MID Selection, Please migrate to Pattern

[nicks8850]

Can someone help me with the exact root cause as what is missing here.

also when I click on test button here it gives me below error.

[Bart T]

You might want to migrate to pattern base cloud discovery:

1. Go to "Pattern Designer" > "Migrate CPG to Pattern"
2. Click "Run Prerequisite Check"
3. Make sure you see on the screen "Prerequisite scan PASSED"
4. Click "Migrate ALL"

For more details please check: 
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827153

[daware-madhu103]

Hello @nicks8850,

  Have you resolved the issue? In my case, we have already migrated to patterns, but we are still unable to select a Mid server.   

[conwayl]

We have migrated to patterns as well and have a multi-cloud provider environment. (one being AWS)

Release: Washington DC 

One adjustment I made was to remove "Cloud Management" from the MID Server - Supported Applications List. (so that AWS MID Servers weren't utilized for other Cloud Provider Schedules)

Also, ensure "AWS" is included in the MID Server - Capabilities

I have seen issues creating schedules from the Cloud Operations Workspace vs. the Discovery Active Schedule views.  However, I do see the ability to select specific MID Servers and MID Server Clusters in both.

Cloud Operations Workspace>Cloud Discovery Home>Schedules:

/now/cloud/discovery-schedules

Discovery Active Schedules:

/now/nav/ui/classic/params/target/%24discovery_schedule_config.do%3Fredirect%3Dview_schedule

[nicks8850]

not yet....we are still facing the same issue.