NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #2624 by repository stars
Latest stable
v1.3000030.2
Last release 13 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Most releases are documented
notes for 50 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
467 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
!Static Badge !Static Badge !Static Badge !Static Badge
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300055.1...v1.300056.0
Features:
Enhancements:
Bug Fixes:
========================================================================
🐞 [ContainerInsights] Fix endpoint slice to capture service name instead of slice name 🐞 by @sky333999 in https://github.com/amazon-contributing/opent
🐞 [ContainerInsights] Fix endpoint slice to capture service name instead of slice name 🐞 by @sky333999 in https://github.com/amazon-contributing/opentelemetry-collector-contrib/pull/314
This change fixes a bug between v1.300054.0 and v1.300055.1 where the agent would incorrectly send the Service as the name of the endpoint slice as opposed to the name of the service itself on the Container Insights metrics.
Nothing published for this version
Nothing published for this version
Nothing published for this version
!Static Badge !Static Badge !Static Badge !Static Badge
💡 [Core] Go1.24 bump by @Paramadon in https://github.com/aws/amazon-cloudwatch-agent/pull/1623 💡
The same artifacts as v1.300055.0 but built with Go 1.24.
Enhancements:
========================================================================
!Static Badge !Static Badge !Static Badge !Static Badge
🐞 [Prometheus/AMP] Add deltatocumulativeprocessor for AMP destinations 🐞 by @dricross in https://github.com/aws/amazon-cloudwatch-agent/pull/1624 When using CWAgent to scrape Prometheus metrics and publish to Amazon Managed Prometheus (AMP), the agent would previously drop any non-cumulative delta metrics, leading to a potential loss in observability. This bug fixes the issue by inserting a delta to cumulative processor in the pipeline such that we no longer drop these metrics.
🐞[Application Signals] Fix service ip to workload mapping in an edge case 🐞 by @pxaws in https://github.com/aws/amazon-cloudwatch-agent/pull/1644 An edge case was introduced in v1.300053.0 where a K8s Service backed by one pod that is terminated can trigger a race condition resulting in the agent not mapping the pod's IP to the corresponding application/workload - thus breaking the Application Signals topology & experience. This fixes the race condition by accounting for delayed termination of pods when populating the PodIP <-> Service cache.
💡 [Explore Related] Support entity for OTLP custom metrics / Add service entity support for EMF exporter 💡by @musa-asad in https://github.com/aws/amazon-cloudwatch-agent/pull/1529 CWAgent now supports attaching Entity information (namespace, node name & application/workload) for OTLP custom metrics sent to it. This expands the coverage of Exploring Related telemetry to use cases utilizing the agent's standalone OTLP plugin for metrics (even when Application Signals is not being used).
💡 [Explore Related] Implement Kubernetes Metadata Extension 💡 by @musa-asad in https://github.com/aws/amazon-cloudwatch-agent/pull/1605 In order to facilitate attaching entity for use cases outside of Application Signals, CWAgent needs the ability to map a Source IP back to the corresponding application/workload. This change introduces a new re-usable extension that extracts the logic to map a Source IP to a workload into a common place that can then be used for Application Signals, Explore Related & other use cases in the future.
💡 [Explore Related] Add platform type for Container Insights in EKS 💡by @zhihonl in https://github.com/aws/amazon-cloudwatch-agent/pull/1638 Container logs published to Container Insights log groups cannot be distinguished for EKS vs native K8s today and this results in Container Insights metrics not being properly correlated to Container Insights application logs. With this enhancement, the agent now sets the Platform Type (EKS vs native K8s) on the log events to facilitate correct correlation between metrics & logs for customers leveraging Explore Related.
💡 [Core] Reduce noisy warning log in CI podresourcesstore / Reduce noisy logs with prometheus receiver 💡 by @okankoAMZ in https://github.com/amazon-contributing/opentelemetry-collector-contrib/pull/300 and by @movence in https://github.com/amazon-contributing/opentelemetry-collector-contrib/pull/297 These enhancements reduce the verbosity of noisy logs printed by the agent in scenarios when Enhanced Container Insights is enabled and also on non-GPU Kubernetes clusters. These logs were previously polluting the agent logs with noise, leading to confusion when triaging genuine issues.
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300054.0...v1.300055.0
Features:
Enhancements:
Bug Fixes:
========================================================================
💡 [Core] Go1.24 bump by @Paramadon in https://github.com/aws/amazon-cloudwatch-agent/pull/1623 💡 The same artifacts as v1.300054.0 but built with Go 1
💡 [Core] Go1.24 bump by @Paramadon in https://github.com/aws/amazon-cloudwatch-agent/pull/1623 💡
The same artifacts as v1.300054.0 but built with Go 1.24.
!Static Badge !Static Badge !Static Badge !Static Badge
🐞 [OTLP] Drop metric if it has nil value in cloudwatch exporter 🐞 by @musa-asad in https://github.com/aws/amazon-cloudwatch-agent/pull/1608 OTLP metrics that did not specify a value and sent to the CWAgent would cause it to panic & crash. This bug fix improves the resiliency by filtering out such metrics prior to publishing to CloudWatch.
🐞 [Container Insights] Handle bearer token rotation 🐞 by @rvasahu-amazon & @movence in https://github.com/amazon-contributing/opentelemetry-collector-contrib/pull/285 & https://github.com/amazon-contributing/opentelemetry-collector-contrib/pull/292 As part of Container Insights, CWAgent scrapes Control Plane metrics and uses a Bearer Token to authenticate itself. These tokens expire after 90 days, after which the agent previously would not pick up the new token unless restarted. With this change, we pick up the renewed tokens without requiring any manual intervention.
🚀 [Logs] Configure Backpressure mode to release file descriptors 🚀 by @movence in https://github.com/aws/amazon-cloudwatch-agent/pull/1577
Backpressure is a scenario where the agent is unable to publish logs at the same rate at which logs are being read (or unable to publish entirely due to CloudWatch being unavailable for example). A common symptom in such scenarios is that the agent does not release the file descriptors, thus consuming disk space even though a file is "deleted", causing the host to run out of disk eventually.
CWAgent offers a new capability to configure the mode when facing Backpressure while publishing logs to CloudWatch. Setting backpressure_mode to fd_release now dictates the agent to release file descriptors when facing backpressure.
🚀 [Logs] Ability to trim timestamp in log messages 🚀 by @zhihonl & @nathalapooja in https://github.com/aws/amazon-cloudwatch-agent/pull/1582
CWAgent now provides the ability to trim timestamps before publishing log events to CloudWatch Logs. Often times, the timestamp in a log message is redundant since its already present as a field on the CloudWatch Log event. This new opt-in feature, trim_timestamp, can help reduce the size of bytes ingested to CloudWatch Logs.
🚀 [Container Insights] Add EFA device level metrics 🚀 by @Aakash-Dantre in https://github.com/aws/amazon-cloudwatch-agent/pull/1594 As part of EFA metrics for Enhanced Container Insights, we now publish more granular metrics at a EFA Device level, thus enhancing the observability of EFA devices by linking them to their corresponding ENI IDs in AWS. This in turn makes it easier to correlate EFA metrics with network interface resources.
💡 [Container Insights] Use endpoint slices instead of endpoints 💡 by @nathalapooja in https://github.com/aws/amazon-cloudwatch-agent/pull/1593 CWAgent now uses the better & optimized Endpoint Slices API instead of the legacy Endpoints API when fetching service metadata for Container Insights. This helps improve the performance of the agent, especially on the impact the agent has on the K8s API Server for large clusters running 1000s of nodes.
💡 [Disk] Pick up new volumes every 5 mins 💡 by @lisguo in https://github.com/aws/amazon-cloudwatch-agent/pull/1578
CWAgent would only discover volumes only upon start and would not refresh them after. This meant metrics for new volumes created after the agent start would miss the VolumeId dimension.
CWAgent now sets RefreshVolumesInterval to a default of 5mins if VolumeId is configured as an append_dimension, thus ensuring the VolumeId dimension is present as expected.
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300053.0...v1.300054.0
Features:
Enhancements:
Bug Fixes:
========================================================================
Nothing published for this version
Nothing published for this version
Nothing published for this version
With the launch of EKS access entries, aws-auth is considered deprecated. So we now switched to a better mechanism to inspect the issue field in the s…
🐞 [Logs] Only add to cache if log stream is created 🐞 by @jefchien in https://github.com/aws/amazon-cloudwatch-agent/pull/1566 This change fixes a bug in v1.300052.0 where if agents installed in a fleet/cluster are writing to log streams in the same log group, there could be a race condition where one agent creates the log group and the others detect the presence of the log group falsely as a success and caches the same, preventing them from trying to re-create the log stream and successfully publishing logs.
🐞 [Core] Take entity data into account for payload size 🐞 by @varunch77 in https://github.com/aws/amazon-cloudwatch-agent/pull/1483 This change fixes a bug between v1.300049.1 and v1.300052.0 where in some edge cases, the agent can miscalculate the overall size of a request and not batch the metrics effectively.
💡 [Application Signals] Add endpoint slice watcher 💡 by @pxaws in https://github.com/aws/amazon-cloudwatch-agent/pull/1528
The startup logic in Application Signals was previously calling expensive list API calls to the /pods endpoint on the K8s API Server, overloading the control plane for large clusters. With this optimization, we switched to a less expensive list/watch mechanism for /endpointslices, retrieving a lot less information that is actually required for the Application Signals experience.
💡 [Logs] Reduce PutRetentionPolicy calls by checking existing policy 💡 by @movence in https://github.com/aws/amazon-cloudwatch-agent/pull/1545 Previously, the agent would make a PutRetentionPolicy API call for every log group every time it restarted, thus causing throttling issues. With this enhancement, the agent first checks if the Retention Policy is already set by calling DescribeLogGroup and only sets it if required. It also now does this asynchronously and with a jitter & exponential backoff.
💡 [Explore Related] Scrape auto scaling group attributes from resource metrics 💡 by @zhihonl in https://github.com/aws/amazon-cloudwatch-agent/pull/1521 Previously, if IMDS tags are disabled, the agent would not set the ASG on the entity even though it can be retrieved through ectagger using the Describe API. We now retrieve ASG from ec2tagger for entity even when IMDS tags are not enabled
💡 [Explore Related] Add entity processor to the otlp metrics and logs pipeline 💡 by @duhminick in https://github.com/aws/amazon-cloudwatch-agent/pull/1504 Extends support for setting entities for the OTLP flows both in the metrics and logs section when running on EKS to provide an even richer Explore Related experience
💡 [Core] Changing log level of cert watcher from error to debug 💡 by @mitali-salvi in https://github.com/aws/amazon-cloudwatch-agent/pull/1531 Reduce verbosity of a non-impacting warning to reduce clutter
💡 [Core] Fix EKS cluster detection 💡 by @musa-asad in https://github.com/aws/amazon-cloudwatch-agent/pull/1532
The agent previously relied on the existence of aws-auth config map to know if it was running on EKS. With the launch of EKS access entries, aws-auth is considered deprecated. So we now switched to a better mechanism to inspect the issue field in the service account when determining if we are running on EKS
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300052.0...v1.300053.0
Bug Fixes:
Enhancements:
========================================================================
🐞 Only add to cache if log stream is created 🐞 by @jefchien in https://github.com/aws/amazon-cloudwatch-agent/pull/1566 This change fixes a bug in v1.
🐞 Only add to cache if log stream is created 🐞 by @jefchien in https://github.com/aws/amazon-cloudwatch-agent/pull/1566 This change fixes a bug in v1.300052.0 where if agents installed in a fleet/cluster are writing to log streams in the same log group, there could be a race condition where one agent creates the log group and the others detect the presence of the log group falsely as a success and caches the same, preventing them from trying to re-create the log stream and successfully publishing logs.
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300052.0...v1.300052.1
Nothing published for this version
Nothing published for this version
!Static Badge !Static Badge !Static Badge !Static Badge
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300051.0...v1.300052.0
Bug Fixes:
Enhancements:
========================================================================
Nothing published for this version
!Static Badge !Static Badge !Static Badge !Static Badge
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300050.0...v1.300051.0
Nothing published for this version
[Prometheus] Introduce OTel Prometheus Receiver for publishing to AMP
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300049.1...v1.300050.0
Nothing published for this version
!Static Badge !Static Badge !Static Badge !Static Badge
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300048.1...v1.300049.1
Nothing published for this version
Nothing published for this version
[Metrics/Logs] Annotate Infra, statsD, collectD metrics and application logs with entities
Enhancements:
========================================================================
Nothing published for this version
[ContainerInsights] Use LocalNode decorator for DCGM and Neuron metrics
Enhancements:
========================================================================
Nothing published for this version
!Static Badge !Static Badge !Static Badge !Static Badge
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300047.0...v1.300048.1
Bug Fixes:
========================================================================
Nothing published for this version
Support OTLP receiver for metrics
Features:
Enhancements:
Bug Fixes:
========================================================================
Nothing published for this version
Nothing published for this version
Nothing published for this version
!Static Badge !Static Badge !Static Badge !Static Badge
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300045.1...v1.300047.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[ApplicationSignals] EKS resource detector is now no-op on non-EKS environments by @jefchien in https://github.com/aws/amazon-cloudwatch-agent/pull/13
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300044.0...v1.300045.1
Bug Fixes:
Enhancements:
========================================================================
Nothing published for this version
[ApplicationSignals] Fix EKS detector nil panic
Bug Fixes:
Enhancements:
========================================================================
[ContainerInsights] Deprecate runtime tag from neuron metrics to fix false average calculation by @sam6134 in https://github.com/aws/amazon-cloudwatch…
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300043.0...v1.300044.0
Bug Fixes:
Enhancements:
========================================================================
Nothing published for this version
Nothing published for this version
[Metrics/Plugin] Drop original metrics support added for statsd, collectd and ethtool metrics by @musa-asad in https://github.com/aws/amazon-cloudwatc
Full Changelog: https://github.com/aws/amazon-cloudwatch-agent/compare/v1.300042.1...v1.300043.0
Bug Fixes:
Enhancements:
========================================================================
Nothing published for this version
One column per quarter.