Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Troubleshoot issues in Network Flow Monitor

Focus mode
Troubleshoot issues in Network Flow Monitor - Amazon CloudWatch

This section provides guidance for troubleshooting errors with Network Flow Monitor, including solving issues with installing agents.

Troubleshoot issues in EKS agents installation

When you try to upgrade the AWS Network Flow Monitor Agent add-on for EKS from v1.0.0 to v1.0.1 in AWS Management Console, you might receive the following error message:

"Service account aws-network-flow-monitoring-agent-service-account in pod identity configuration is not supported for addon aws-network-flow-monitoring-agent."

This error is returned because a resource was renamed. The EKS add-on v1.0.1 changes the service account name from aws-network-flow-monitoring-agent-service-account to aws-network-flow-monitor-agent-service-account.

Then, if Not set is not selected in the console, the pod identity association is not reset to the new resource name.

To fix this issue, do the following when you upgrade to the new version by using the console:

  1. Under Pod Identity IAM role for service account, select Not set.

  2. Select New version (v1.0.1).

  3. Select Upgrade.

  4. Choose Save changes.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.