Service Mapping using Service Graph for AWS

[Mark Smith5]

Hi,

We have been trying to get service mapping working for over a year with no success.

TAG based mapping failed - people dependency in a large estate

Pattern based mapping failed - Permissions required for linux and windows in aws estate is too invasive

In order to use Traffic based or Predictive Intelligence we need two things:  tcp data and process data

We decided to use the SG for AWS plugin to get this data.  This worked better than Pattern as it uses SSM to execute commands via API and is a better solution overall.

Now we have the data and are attempting Traffic based or Predictive Intelligence.

It appears that mapping this way requires Pattern based discovery?

Seeing that we now have the data .. how do we force the Traffic based or Predictive Intelligence mapping using SG for AWS and not patterns?

[Mark Smith5]

So I found this chart presented in one of the Service Mapping Youtube videos.  If I understand this correctly .. None of the service graph capabilities can be used for ML Connections.

For SG-AWS this does not make sense as it collects TCP connection and running process information directly from the AWS EC2's.  According to ML Connections documentation - these two pieces of information are all that is required.

Contradictory or am I missing something?

[Mark Smith5]

SNOW Gurus please respond.

[Mark Smith5]

BUMP!

[Mel Saligumba3]

Interested on reply please!