reference deployment

Prometheus for Amazon EKS

Monitor containerized applications at scale

This Quick Start deploy Prometheus open-source monitoring for Amazon Elastic Kubernetes Service (Amazon EKS). It uses Prometheus query language (PromQL) to monitor the performance of containerized workloads without the need for underlying infrastructure. You can use the Kubernetes API server to ingest  metrics from Amazon EKS nodes and self-managed clusters. For visualization, Prometheus features an expression browser and offers multiple modes of graphing and dashboard support.

Amazon Web Services (AWS) customers can deploy Prometheus into a new virtual private cloud (VPC) and an Amazon EKS cluster, an existing VPC and a new cluster, or an existing VPC and an existing cluster. 

This Quick Start was developed by AWS.

  •  What you'll build
  • Use this Quick Start to set up the following environment on AWS. Note that this module is based on the Modular and Scalable Amazon EKS Architecture Quick Start.

    • A Kubernetes namespace for Prometheus.
    • Node-exporter DaemonSet with a pod to monitor Amazon EKS nodes.
    • Pushgateway deployment with a pod to push metrics from short-lived jobs to intermediary jobs that Prometheus can scrape.
    • Kube-state-metrics DaemonSet with a pod to monitor the Kubernetes API server.
    • Server StatefulSet with a pod and attached persistent volume (PV) to scrape and store time-series data. The pod uses persistent volume claims (PVCs) to request PV resources.
    • Alertmanager StatefulSet with a pod and attached PV for deduplication, grouping, and routing of alerts.
    • Amazon Elastic Block Storage (Amazon EBS) General Purpose SSD (gp2) storage volume.
  •  How to deploy
  • To build Prometheus for Amazon EKS, follow the instructions in the deployment guide. The deployment process takes about 1.5 hours and includes these steps:

    1. If you don't already have an AWS account, sign up at, and sign into your account.
    2. Prepare an existing EKS cluster.
    3. Launch the Quick Start. Before you create the stack, choose the AWS Region from the top toolbar.
    4. Test the deployment.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

  •  Cost and licenses
  • You are responsible for the cost of the AWS services and any third-party licenses used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.

    The AWS CloudFormation templates for this Quick Start include configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy the Quick Start, create AWS Cost and Usage Reports to track costs associated with the Quick Start. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information about the report, see What are AWS Cost and Usage Reports?