AWS Security ChangesHomeSearch

AWS AmazonCloudWatch: Document default-on features and OTLP endpoint ports for EKS add-on

Service: AmazonCloudWatch · 2026-11-21 · Documentation medium

File: AmazonCloudWatch/latest/monitoring/install-CloudWatch-Observability-EKS-addon.md · Type: network

Summary

Adds a 'Features that are on by default' table for add-on/Helm chart v8.0.0+ (including always-on OpenTelemetry service identity and telemetry filters), notes that the add-on now serves its own OTLP endpoint on ports 4317/4318 by default, updates OTLP receiver examples to bind 0.0.0.0:14318 to avoid port conflicts, and fixes Container Insights links and nav titles.

Security assessment

The change documents that the add-on/chart now expose an OTLP receiver on ports 4317/4318 by default and updates examples to bind 0.0.0.0:14318, which is a network-exposure/configuration consideration for cluster telemetry ingestion; the new defaults table also surfaces always-on OpenTelemetry service identity and telemetry filters. No specific vulnerability, CVE, or incident is referenced, so this is security-adjacent config guidance rather than a fix.

Evidence

In version 8.0.0 and later, the add-on and the chart serve their own OTLP endpoint on ports 4317 and 4318 by default. An OTLP receiver in your configuration must use other ports, as in the following examples, or the agent can't bind the port and doesn't start. For more information, see [OTLP ingestion](./eks-observability-addon-otlp-endpoint.html).

Diff

diff --git a/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Observability-EKS-addon.md b/AmazonCloudWatch/latest/monitoring/install-CloudWatch-Observability-EKS-addon.md
index 9da2117..63c1c70 100644
--- a//AmazonCloudWatch/latest/monitoring/install-CloudWatch-Observability-EKS-addon.md
+++ b//AmazonCloudWatch/latest/monitoring/install-CloudWatch-Observability-EKS-addon.md
@@ -7 +7 @@
-Option 1: Install using EKS Pod IdentityOption 2: Install with IAM permissions on worker nodesOption 3: Install using IAM service account role (applies only to using the add-on)(Optional) Additional configurationCollect Java Management Extensions (JMX) metricsEnable Kueue metricsAppending OpenTelemetry collector configuration filesApplication Signals configurationConsiderations for large Kubernetes clustersConsiderations for Amazon EKS Hybrid NodesTroubleshootingOpt out of Application Signals
+Features that are on by defaultOption 1: Install using EKS Pod IdentityOption 2: Install with IAM permissions on worker nodesOption 3: Install using IAM service account role (applies only to using the add-on)(Optional) Additional configurationCollect Java Management Extensions (JMX) metricsEnable Kueue metricsAppending OpenTelemetry collector configuration filesApplication Signals configurationConsiderations for large Kubernetes clustersConsiderations for Amazon EKS Hybrid NodesTroubleshootingOpt out of Application Signals
@@ -13 +13 @@ You can use either the Amazon CloudWatch Observability EKS add-on or the Amazon
-Using either method on an Amazon EKS cluster enables both [Container Insights](./deploy-container-insights-EKS.html) for Amazon EKS and [CloudWatch Application Signals](./CloudWatch-Application-Monitoring-Sections.html) by default. Both features help you to collect infrastructure metrics, application performance telemetry, and container logs from the cluster.
+Using either method on an Amazon EKS cluster enables both [Container Insights](./ContainerInsights.html) for Amazon EKS and [CloudWatch Application Signals](./CloudWatch-Application-Monitoring-Sections.html) by default. Both features help you to collect infrastructure metrics, application performance telemetry, and container logs from the cluster. From version 8.0.0, the add-on and the chart also serve an OTLP endpoint and scrape ServiceMonitor and PodMonitor targets by default. For the full list, see Features that are on by default.
@@ -33,0 +34,2 @@ When you install the add-on or the Helm chart, you must also grant IAM permissio
+  * Features that are on by default
+
@@ -60,0 +63,15 @@ When you install the add-on or the Helm chart, you must also grant IAM permissio
+## Features that are on by default
+
+The following table lists what version 8.0.0 and later of the add-on and the Helm chart turn on when you install them without configuration values, by top-level configuration value. To change a default, pass the configuration value in the second column. Each feature page lists the settings under its value. For how to pass configuration values, see [Configuring the add-on and the Helm chart](./eks-observability-addon-configure.html).
+
+Feature | Configuration value | Default  
+---|---|---  
+[Enhanced Container Insights (Classic)](./container-insights-eks-classic.html) | `containerInsights.enabled` | On  
+Container logs, collected by Fluent Bit | `containerLogs.enabled` | On  
+[Application Signals (Classic)](./eks-observability-addon-application-signals.html) | `applicationSignals.enabled` | On  
+[OTLP ingestion](./eks-observability-addon-otlp-endpoint.html) | `otlp.enabled` | On  
+[Scraping ServiceMonitor and PodMonitor targets](./eks-observability-addon-prometheus-monitors.html) | `otelPrometheusMonitor.enabled` | On  
+[OpenTelemetry service identity](./eks-observability-addon-service-identity.html) | `otelServiceIdentity` | Always on  
+[Telemetry filters](./eks-observability-addon-telemetry-filters.html) | `otelFilters` | Nothing filtered, except a built-in list of high-cardinality pod and node labels  
+[OTel Container Insights (Recommended)](./container-insights-eks-otel.html) | `otelContainerInsights.enabled` | Off  
+  
@@ -292 +309 @@ This method is valid only if you are using the Amazon CloudWatch Observability E
-  * You have a functional Amazon EKS cluster with nodes attached in one of the AWS Regions that supports Container Insights. For the list of supported Regions, see [Container Insights](./ContainerInsights.html).
+  * You have a functional Amazon EKS cluster with nodes attached in one of the AWS Regions that supports Container Insights. For the list of supported Regions, see [Container Insights for Amazon EKS](./ContainerInsights.html).
@@ -834,0 +852,2 @@ To prevent merge conflicts with pipelines automatically created by CloudWatch ag
+In version 8.0.0 and later, the add-on and the chart serve their own OTLP endpoint on ports 4317 and 4318 by default. An OTLP receiver in your configuration must use other ports, as in the following examples, or the agent can't bind the port and doesn't start. For more information, see [OTLP ingestion](./eks-observability-addon-otlp-endpoint.html).
+
@@ -847 +866,2 @@ or
-            http: {}
+            http:
+              endpoint: 0.0.0.0:14318
@@ -865 +885,2 @@ or
-        http: {}
+        http:
+          endpoint: 0.0.0.0:14318
@@ -1075 +1096 @@ You can further customize each agent installation by adding `nodeSelector`, `tol
-Node-level metrics aren't available for hybrid nodes because [Container Insights](./ContainerInsights.html) depends on the availability of the [EC2 Instance Metadata Service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html) (IMDS) for node-level metrics. Cluster, workload, Pod, and container-level metrics are available for hybrid nodes.
+Node-level metrics aren't available for hybrid nodes because [Container Insights for Amazon EKS](./ContainerInsights.html) depends on the availability of the [EC2 Instance Metadata Service](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html) (IMDS) for node-level metrics. Cluster, workload, Pod, and container-level metrics are available for hybrid nodes.
@@ -1175 +1196 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Sending logs to Amazon CloudWatch
+EKS Container Insights
@@ -1177 +1198 @@ Sending logs to Amazon CloudWatch
-Advanced configuration for OTel Container Insights on Amazon EKS
+Configuring the add-on and the Helm chart