cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 11
Report Inappropriate Content
Message 1 of 5

AWS generating traffic discovery errors for unused regions

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?

4 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 5

Re: AWS generating traffic discovery errors for unused regions

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

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Level 11
Report Inappropriate Content
Message 3 of 5

Re: AWS generating traffic discovery errors for unused regions

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

Re: AWS generating traffic discovery errors for unused regions

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

Level 11
Report Inappropriate Content
Message 5 of 5

Re: AWS generating traffic discovery errors for unused regions

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.

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community