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 allows you to more easily integrate applications with other Amazon Web Services services.
With Amazon Managed Service for Apache Flink, you pay only for what you use. There are no resources to provision and no upfront costs. You are charged an hourly rate based on the number of Kinesis Processing Units (KPUs) used to run your applications. 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 guidance on KPU usage
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 prior to testing your application is 1 MB per second per KPU.
China (Ningxia) region:
| Kinesis Processing Unit, Per Hour | ¥ 0.777 per hour |
| Running Application Storage, Per GB-month (50 GB of running application storage is assigned per Kinesis Processing Unit) | ¥ 0.664 per GB-month |
| Durable Application Storage, Per GB-month | ¥ 0.176 per GB-month |
| Kinesis Processing Unit, Per Hour for Studio notebooks | ¥ 0.777 per hour |
| Running Application Storage, Per GB-month for Studio Notebooks | ¥ 0.664 per GB-month |
China (Beijing) region:
| Kinesis Processing Unit, Per Hour | ¥ 1.161 per hour |
| Running Application Storage, Per GB-month (50 GB of running application storage is assigned per Kinesis Processing Unit) | ¥ 0.746 per GB-month |
| Durable Application Storage, Per GB-month | ¥ 0.195 per GB-month |
| Kinesis Processing Unit, Per Hour for Studio notebooks | ¥ 1.161 per hour |
| Running Application Storage, Per GB-month for Studio Notebooks | ¥ 0.746 per GB-month |
Pricing examples
Pricing Example 1: Studio Notebook with a Simple Streaming Filter
A customer uses an Apache Flink application in Amazon Managed Service for Apache Flink to read streaming data captured by their Apache Kafka topic in their Amazon MSK cluster. The customer is applying a continuous filter to only retain records of interest. A customer creates one durable application backup per day and retains those backups for seven days. The monthly Amazon Managed Service for Apache Flink charges will be computed as follows:
The price in China (Ningxia) Region is ¥0.777 per KPU-Hour used for the stream processing application. This simple application uses 1 KPU to process the incoming data stream. Each Apache Flink application is charged an additional KPU per application.
30 Days/Month * 24 Hours/Day = 720 Hours/Month
Monthly KPU Charges = 720 Hours/Month * (1 KPU + 1 additional KPU) * ¥0.777 /Hour) = ¥1118.88
Apache Flink applications use 50GB running application storage per KPU and are charged ¥0.664 per GB-month in China (Ningxia) Region.
Monthly Running Application Storage Charges = 720 Hours/Month * 1 KPU * 50GB/KPU * ¥0.664/GB-month = ¥33.20
Apache Flink applications charge ¥0.176 per GB-month in China (Ningxia) Region for durable application backups. Each backup for this application is 1 MB and the customer maintains the 7 most recent backups, creating a new and deleting an old backup every day.
Monthly Durable Application Storage Charges = 7 backups * (1 MB/backup * 1 GB/1000 MB) * ¥0.176 /GB-month = ¥0.001 (rounded)
Total Charges = ¥1118.88 + ¥33.20 + ¥0.001 = ¥1152.081
Pricing Example 2: Studio Notebook with a Sliding Window Deployed to Streaming Mode
A customer uses Amazon Managed Service for Apache Flink Studio to build a sliding window on streaming data captured by a topic in their Amazon MSK cluster. They use a Studio notebook with 2 KPU for 8 hours over two days to develop and test their queries. After development they deploy their application as a streaming application with 12 KPU. Once the streaming application is deployed, they stop their Studio notebook. The streaming application continuously runs with durable state. The customer creates durable state backups every day.
Monthly charges
Developing and testing query Amazon Managed Service for Apache Flink Studio:
KPU charges = 2 Days * 8 Hours * (2 KPU + 2 additional KPU for Studio notebook) * ¥0.777/Hour) = ¥49.728
Apache Flink applications use 50GB running application storage per KPU and charged ¥0.664 per GB-month in China (Ningxia) region.
Running Application Storage Charges = 2 Days * 2 KPU * (50GB * ¥0.664/GB-month) = ¥4.42
Deploying as streaming application to run continuously and take application backups:
KPU charges = 28 Days * 24 Hours *(2 KPU + 1 additional KPU for streaming application) * ¥0.777/Hour) = ¥1566.432
Apache Flink applications use 50GB running application storage per KPU and are charged ¥0.664
Running Application Storage Charges = 28 Days * 2 KPU * (50GB * ¥0.664/GB-month) = ¥61.97
Durable Application Storage Charges = 28* (1 MB/backup * 1 GB/1000 MB) * ¥0.176/GB-month = ¥0.001 (rounded)
Total Charges = ¥49.728 + ¥4.42 + ¥1566.432 + ¥61.97158.40 + $5.00 + ¥0.001 = ¥1682.55163.41
Pricing Example 3: Apache Flink application performing streaming ETL with workload changes
A customer uses an Apache Flink application in Amazon Managed Service for Apache Flink to continuously transform and deliver log data captured by their Kinesis Data Stream to Amazon S3. The log data is transformed using several operators including applying a schema to the different log events, partitioning data by event type, sorting data by timestamp, and buffering data for one hour prior to delivery. The application has many transformation steps but none are computationally intensive. This stream ingests data at 2,000 records/second for 12 hours per day and increases to 8,000 records/second for 12 hours per day. The customer does not create any durable application backups. The monthly Amazon Managed Service for Apache Flink charges will be computed as follows:
Monthly charges
The price in China (Ningxia) Region is ¥0.777 per KPU-Hour. Amazon Managed Service for Apache Flink allocates 50GB of running application storage per KPU and charged ¥0.664 per GB-month.
Heavy Workload: During the 12 hour heavy workload period, the Amazon Managed Service for Apache Flink application is processing 8,000 records/second and automatically scales up to 8 KPUs. After the heavy workload period, the Amazon Managed Service for Apache Flink application scales the application down after 6 hours of lower throughput. The application is scaled up to 8 KPUs for a total of 18 hours per day.
30 Days/Month * 18 Hours/Day = 540 Hours/Month
Monthly KPU Charges = 540 Hours/Month * 8 KPU * ¥0.777/Hour = ¥3356.64
Monthly Running Application Storage Charges = 540 Hours/Month * 8 KPU * 50GB/KPU * ¥0.664/GB-month = ¥868.48
Monthly KPU and Storage Charges = ¥2868.48 + ¥6225.12 = ¥6226.12
Light Workload: During the light workload period for the remaining 6 hours, the Amazon Managed Service for Apache Flink application is processing 2,000 records/second and automatically scales down to 2 KPU.
30 Days/Month * 6 Hours/Day = 180 Hours/Month
Monthly KPU Charges = 180 Hours/Month * 2 KPU * ¥0.777/Hour = ¥279.72
Monthly Running Application Storage Charges = 180 Hours/Month * 2 KPU * 50GB * ¥0.664/GB-month = ¥66.40
Monthly KPU and Storage Charges = ¥279.72 + ¥66.40 = ¥346.12
Each Apache Flink application is charged an additional KPU per application.
Monthly Charges = 30 * 24 * 1 KPU * ¥0.777/Hour = ¥559.44
Total Charges = ¥3622.24 + ¥346.12 + ¥559.44= ¥4527.80
Note: We reserve the right to charge standard Amazon Web Services data transfer costs for data transferred in and out of Amazon Managed Service for Apache Flink applications.
