This integration collected logs from Kubernetes workloads with Fluentd and sent them to AWS CloudWatch Logs. It was useful when a team wanted container logs in the same AWS destination used for other operational records, rather than inspecting each machine separately. The important behavior includes parsing, log-group selection and where reading resumes after a restart. AWS's current Fluent Bit path changes the collector, so those details must be checked during replacement.
Deployment and operating notes
The recovered incubator chart packaged Fluentd for CloudWatch Logs. AWS’s current Container Insights guidance describes Fluent Bit as a DaemonSet and includes specific warnings about overlapping an old Fluentd deployment with the replacement. Fluent Bit and Fluentd have different configuration and plugin models, so changing the image while retaining the old values is not a valid migration.
Inventory log groups, stream naming, retention, region, IAM identity, multiline parsing and excluded namespaces. Confirm the supported AWS integration for the cluster and review the permissions needed to create or write log groups. Test a known application log, stack trace and node event in the expected destination. Compare timestamps and metadata, and watch ingestion volume for duplication during transition. Preserve tail position or document an accepted replay window before disabling the old collector. Keep an emergency log path while testing destination failures. The old chart’s broad monitoring description should not be interpreted as enabling CloudWatch metrics, traces and logs automatically.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
This chart bootstraps a Fluentd Cloudwatch deployment on a Kubernetes cluster using the Helm package manager. Fluentd is an open source data collector, which lets you unify the data collection and consumption for a better use and understanding of data. Whereas, CloudWatch provides you with data and actionable insights to monitor your applications, understand and respond to system-wide performance changes, optimize resource utilization, and get a unified view of operational health.
Why We Use Fluentd?
Simple and Easy yet Flexible
Fluentd can be set up on your laptop in less than 10 minutes. You can download it here and try it right now. Fluentd’s 500+ plugins makes it compatible with dozens of data sources and data outputs. Plugins are easy to write and deploy, too.
Open Source
Fluentd is Apache 2.0 Licensed, fully open source software. That means your imagination, not license restrictions, is the limit of what you can achieve with Fluentd. The source code is available on GitHub.
Proven Reliability and Performance
5,000+ data-driven companies rely on Fluentd to differentiate their products and services through a better use and understanding of their log data. In fact, according to the survey by Datadog, Fluentd is the 7th top technologies running on Docker container environments.
Some Fluentd users collect data from thousands of machines in real-time. Thanks to its small memory footprint (30~40MB), you can save a lot of memory at scale.
Community
The community behind Fluentd keeps improving the software and helps one another to make Fluentd useful for everyone.
Why We Use CloudWatch?
CloudWatch collects monitoring and operational data in the form of logs, metrics, and events, providing you with a unified view of AWS resources, applications and services that run on AWS, and on-premises servers.
You can use CloudWatch to set high resolution alarms, visualize logs and metrics side by side, take automated actions, troubleshoot issues, and discover insights to optimize your applications, and ensure they are running smoothly.
With Amazon CloudWatch, it is easy to get started. There is no up-front commitment or minimum fee; you simply pay for what you use. You will be charged at the end of the month for what you use.
Sources & further reading
Spotted something that needs another look?
Help improve this page →