AWS generating traffic discovery errors for unused regions

[Jmac24]

Getting a bunch of these errors in the audit log and we have been having ongoing issues with getting tons of entries in the stderr.log from CWS. Here's an example from the audit log:

Traffic Discovery Failed for logGroup: log_Mcafee_eu-west-1 :: Unable to execute HTTP request: Connection reset

We will see errors like that for basically every region outside of the ones we have systems in, and these are being generated every couple minutes, as we have a lot of AWS accounts in use. 

Is there a way to modify CWS settings so that we only attempt to connect to regions we are using, since our accounts will not have access to the others and generate the errors?

[cdinet]

I am checking on that - what is cws being used for and what region are you in?

[Jmac24]

We have a bunch of AWS servers being managed with CWS for ENS and Solidcore. We are only using these regions and one I was told is in N-California that I need to find more details on.

• Us-east-1
• Us-east-2
• Us-west-1
• Us-west-2

[nashcoop]

Was there any additional information about these errors?  I just noticed them in my audit logs as well.

[Jmac24]

In our case, there were existing AWS traffic discovery log groups created on the AWS side, CWS tries to create new traffic discovery log rather than use the already existing one in each region. As a result, we get the errors. Support is looking into a way we can set the accounts to use the existing log groups in AWS. Otherwise, they (AWS admins) would have to modify rights to the groups in a way they are not comfortable in doing. I'll follow up if they come up with a solution. We were hoping there is a config file on the ePO server we could adjust to accomplish this since there is nothing in CWS we can find to make this change.