I have a related set of questions that I'm hoping people can answer. The documentation I've found is fairly unclear on how it all works together. We have AWS Discovery and the SNS AWS Config service turned on and I'm trying to make sure I fully understand how things work with each other.
1. Based on what I am reading and what I see in the documentation, the AWS Event driven discovery primarily is digested via a REST API and only certain events will trigger a pattern, which will need a mid sever to process. Am I understanding that correctly? How can we set which mid server processes these events?
Unclear guide 1 - https://docs.servicenow.com/bundle/tokyo-it-operations-management/page/product/it-operations-managem...
2. My assumption the answer to #1 is going to somewhat be by configuring the proper application/capabilities on the mid server. That concept is still confusing to me. Based on my testing it looks like to associate a Cloud Discovery schedule for AWS you need to either have the AWS capability or the Cloud Management capability enabled on the mid server. What's the difference?
How do I know which capability to set on the mid server?
What purpose does "Application" on a mid server play in cloud discovery? I can have no applications set and still associate a mid server to a cloud schedule as long as the capability is present.
Unclear guide 2 - https://docs.servicenow.com/bundle/utah-servicenow-platform/page/product/mid-server/reference/r_MIDS...
