AWS EKS Connector: Critical Data Ingestion Fix for Missing Table Configuration

What Changed

Fixed missing destinationTable configuration in AWS EKS CCF Data Connector by specifying AWSEKSLogs_CL as the target table for Amazon Elastic Kubernetes Service audit log ingestion.

Security Impact (Visibility & Fidelity)

The AWS EKS connector in v3.0.0 had a complete ingestion failure — the empty destinationTable field caused zero data to be ingested by affected deployments since the initial marketplace release.

Deployments running v3.0.0 have had no visibility into EKS audit events (pod creation, service configuration, RBAC changes, API server activity) — a critical blind spot for Kubernetes security monitoring.

Connector Configuration Fix

CCF pollingConfig now correctly routes compressed JSON logs from Amazon EKS API to AWSEKSLogs_CL custom log table, enabling threat detection against Kubernetes control plane activity.

Affected Files

Solutions/AWS EKS/Data Connectors/AWSEKS_PollingConfig.json
(packaging artefacts: 3.0.0.zip, mainTemplate.json)