Resource Guide for InfluxDB and AWS

Navigate to:

InfluxDB Cloud runs natively on AWS. This is great for users that already rely on AWS because it keeps everything (or at least most things, hopefully!) in one place. This can also reduce data latency, if the region you use is geographically close to your data sources. Plus, it’s super easy to get started using InfluxDB on AWS.

One of the great things about AWS is that it has a ton of different services and features that allow you to do more with your data. Of course, with so many options to choose from, it can also be a challenge to figure out what works with InfluxDB, what’s supported, and what you can do with the combined power of InfluxDB and AWS.

The following is a list of all the different AWS services that currently have integrations with InfluxDB. If you’re looking for something that isn’t here, you can always build your own. (Check out this InfluxDB University course on Telegraf for more info on building custom plugins!)


For many, CloudWatch is a key service for understanding and tracking system performance. InfluxDB has plugins that allow you to interact with CloudWatch in different ways.

To get metrics from CloudWatch into InfluxDB, use the CloudWatch Input Plugin. If you just want to pull CloudWatch alarm data into InfluxDB, use the CloudWatch Alarms Plugin.

If you need your data to go the opposite direction, from InfluxDB to CloudWatch you can use the CloudWatch Output Plugin. There’s also a plugin specifically designed to handle log files, so if you want to use CloudWatch as a central repository for log files, you can export them from InfluxDB to CloudWatch using the CloudWatch Logs Output Plugin.

We even have a CloudWatch template you can use with InfluxDB Cloud that creates dashboards for monitoring CloudWatch with just a few clicks.

EC2, ECS, and Fargate

You can use the ECS Metrics Plugin to monitor performance metrics across several AWS services, including EC2 virtual machines, ECS containers, and Fargate containers. The Telegraf ECS plugin is Fargate compatible, and uses the Amazon ECS v2 metadata and stats API endpoints to gather stats on running containers in a task. You can also leverage more general plugins for broader monitoring operations to bring all your metrics together in one place, including system and Docker monitoring plugins.


If you use Kinesis to process data, you can use the Kinesis Consumer Plugin to tap into that data and pull time series data from Kinesis directly into InfluxDB. We even have a Kinesis Output Plugin that is still in the experimental phase, but can help reduce the total number of API calls you need to make when sending data to Kinesis.


If you run Kubernetes in AWS EKS, the Kubernetes Inventory and Kubernetes Monitoring plugins help you keep track of the assets you have running and how they’re performing.


For AWS Lambda users, InfluxDB has a template you can use to monitor all your Lambda functions. Like the CloudWatch template, it just takes a few minutes to configure before it’s up and running.

In addition to these tools that help you work with specific AWS services, Telegraf has hundreds of plugins. So, if you have data from a source that you want to get into AWS, chances are there is a plugin you can use with Telegraf to do the job for you.

To learn more about InfluxDB and AWS, check out our AWS Partner page. It includes resources, blogs, customer use cases, and more to help you find the solution that works best for you.

If you want to try out InfluxDB, you can even sign up directly from the AWS Marketplace. InfluxDB and AWS are a match made in… well, the cloud!