Amazon Managed Service for Apache Flink Pricing

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 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.

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.

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.

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.

You use Amazon Managed Service for Apache Flink Studio to continuously filter streaming data captured by your Amazon Kinesis Data Streams and only retain records of interest. You want the ability to view and visualize records in real time and easily write queries and programs in SQL and Python. You do not want durable state backups. You provision 4 KPUs for your Studio notebook based on your input stream’s throughput. Your monthly Amazon Managed Service for Apache Flink charges will be computed as follows:

Monthly charges

The price in U.S. East (N. Virginia) Region is $0.11 per KPU/hour used for your stream processing application. This simple application uses 4 KPUs to process the incoming data stream. Each Studio notebook application (example: interactive mode) is charged 2 additional KPUs per application. Monthly KPU Charges = 30 Days * 24 Hours * ([4 KPUs + 2 additional KPUs] * $0.11/ Hour) = $475.20

Apache Flink applications use 50 GB running application storage per KPU and are charged $0.10 per GB/month in US-East-1.

Monthly Running Application Storage Charges = 30 Days * 24 Hours * 4 KPUs * (50GB * $0.10/GB/month) = $20.00 

Total Charges = $475.20 + $20.00 = $495.20

 

You use Amazon Managed Service for Apache Flink Studio to build a sliding window on streaming data captured by a topic in your Amazon Managed Streaming for Apache Kafka (Amazon MSK) cluster. You use a Studio notebook with 4 KPUs for eight hours over two days to develop and test your queries. After development, you deploy the application as a streaming application with 12 KPUs. Once the streaming application is deployed, you stop your Studio notebook. The streaming application can use durable application state and you create durable state backups every day.

The price in U.S. East (N. Virginia) Region is $0.11 per KPU/hour used for your stream processing application.

Monthly charges

Developing and testing query Amazon Managed Service for Apache Flink Studio:
KPU charges = 2 Days * 8 Hours * (4 KPUs + 2 additional KPUs for Studio notebook) * $0.11/Hour) = $10.56

Apache Flink applications use 50 GB running application storage per KPU and charged $0.10 per GB/month in US-East-1.

Running Application Storage Charges = 2 Days * 8 hours * 4 KPUs * (50GB * $0.10/GB-month) = $0.44

Deploying as streaming application to run continuously and take application backups:

KPU charges = 28 Days * 24 Hours * (2 KPUs + 1 additional KPU for streaming application) * $0.11/Hour) = $221.76

Apache Flink applications use 50 GB running application storage per KPU and charged $0.121 per GB/month in US-East-1.

Running Application Storage Charges = 28 Days * 24 Hours * 2 KPUs * (50GB * $0.10/GB-month) = $9.33

Durable Application Storage Charges = 28* (1 MB/backup * 1 GB/1,000 MB) * 0.023/GB-month = $0.01 (rounded to the nearest penny)

Total Charges = $10.56 + $0.44 + $221.76 + $9.33 + $0.01 = $242.10

You use an Apache Flink application in Amazon Managed Service for Apache Flink to continuously transform and deliver log data captured by your Kinesis Data Streams to Amazon Simple Storage Service (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. You do 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 U.S. East (N. Virginia) Region is $0.11 per KPU-hour. Amazon Managed Service for Apache Flink allocates 50 GB of running application storage per KPU and charges $0.10 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 KPUs * $0.11/Hour= $475.20

Monthly Running Application Storage Charges = 540 Hours/Month * 8 KPUs * 50GB/KPUs * $0.10/GB-month = $30.00

Monthly KPU and Storage Charges = $475.20 + $30.00 = $505.20

Light Workload: During the light workload period for the remaining six hours, the Amazon Managed Service for Apache Flink application is processing 2,000 records/second and automatically scales down to 2 KPUs.

30 Days/Month * 6 Hours/Day = 180 Hours/Month

Monthly KPU Charges = 180 Hours/Month * 2 KPUs * $0.11/Hour = $39.60

Monthly Running Application Storage Charges = 180 Hours/Month * 2 KPUs * 50GB * $0.10/GB- month = $2.50

Monthly KPU and Storage Charges = $39.60 + $2.50 = $42.10

Each Apache Flink application is charged an additional KPU per application.

Monthly Charges = 30 * 24 * 1 KPU * $0.11/Hour = $79.20

Total Charges = $505.20 + $42.10 + $79.20 = $626.50