Build end-to-end streaming pipelines with Amazon Managed Service for Apache Flink Blueprints with a single click. Learn more.
Introduction
Transform and analyze streaming data in real time using Apache Flink
With Amazon Managed Service for Apache Flink, you can transform and analyze streaming data in real time using Apache Flink, an open source framework and engine for processing data streams. Amazon Managed Service for Apache Flink simplifies building and managing Apache Flink workloads and help you to more easily integrate applications with other AWS services.
With amazon Managed Service for Apache Flink you are charged for duration and number of KPUs , billed in one-second increments. A single KPU comprises 1 vCPU compute and 4 GB of memory.
Amazon Managed Service for Apache Flink streaming applications pricing
For Apache Flink applications, you are charged a single additional KPU per application, used for orchestration. Applications are also charged for running storage and durable backups. Running application storage is used for stateful processing capabilities in Amazon Managed Service for Apache Flink and is charged per GB/month. Durable backups are optional and provide point-in-time recovery for applications, charged per GB/month.
In streaming mode, Amazon Managed Service for Apache Flink automatically scales the number of KPUs required by your stream processing application as the demands of memory and compute fluctuate. You may choose to provision your application with the number of KPUs required.
Amazon Managed Service for Apache Flink Studio pricing
You are charged two additional KPUs per Studio application in interactive mode. One KPU is used for Apache Flink application orchestration and the other for the serverless interactive development environment. You will also be charged for running application storage used for stateful processing capabilities. Running application storage is charged per GB/month.
When developing in the Studio notebook, you will not have the option to create durable application backups. However, when you deploy your application in the Studio notebook from interactive mode to streaming mode, you will be able to create durable application backups.
General KPU usage guidance
We recommend that you test your application with production loads to get an accurate estimate of the number of KPUs required for your application. KPU usage can vary considerably based on your data volume and velocity, code complexity, integrations, and more. This is especially true when using Apache Flink runtime in Amazon Managed Service for Apache Flink. For example, through internal testing we have observed throughput of hundreds of MB per second per KPU for simple applications with no state, and throughput of less than 1 MB per second per KPU for complex applications that use intensive machine learning (ML) algorithms. With these caveats in mind, the general guidance we provide before testing your application is 1 MB per second, per KPU.