Creating a Managed Service for Apache Flink application - Managed Service for Apache Flink

Amazon Managed Service for Apache Flink was previously known as Amazon Kinesis Data Analytics for Apache Flink.

Creating a Managed Service for Apache Flink application

This topic contains information about creating a Managed Service for Apache Flink.

Building your Managed Service for Apache Flink application code

This section describes the components you use to build the application code for your Managed Service for Apache Flink application.

We recommend that you use the latest supported version of Apache Flink for your application code. The latest version of Apache Flink that Managed Service for Apache Flink supports is 1.18.1. For information about upgrading Managed Service for Apache Flink applications, see Upgrading applications.

You build your application code using Apache Maven. An Apache Maven project uses a pom.xml file to specify the versions of components that it uses.

Note

Managed Service for Apache Flink supports JAR files up to 512 MB in size. If you use a JAR file larger than this, your application will fail to start.

Use the following component versions for Managed Service for Apache Flink applications:

Component Version
Java 11 (recommended)
Scala Beginning with version 1.15, Flink is Scala-agnostic. You can use the version you prefer. Scala 3.3 (LTS) works with Managed Service for Apache Flink 1.18 runtime.
Managed Service for Apache Flink Runtime (aws-kinesisanalytics-runtime) 1.2.0
AWS Kinesis Connector (flink-connector-kinesis) 4.2-1.18
AWS Kinesis Connector (flink-connector-kinesis-streams) [Sink] 4.2-1.18
Apache Beam (Beam applications only) As of March 1, 2024, there is no compatible Apache Flink Runner for Flink 1.18. See Flink Version Compatibility.

Applications can now use the Java API from any Scala version. You must bundle the Scala standard library of your choice into your Scala applications.

For an example of a pom.xml file for a Managed Service for Apache Flink application that uses Apache Flink version 1.18.1, see the Managed Service for Apache Flink Getting Started Application.

For information about creating a Managed Service for Apache Flink application that uses Apache Beam, see Using Apache Beam.

When using Managed Service for Apache Flink Runtime version 1.1.0 and later, you specify the version of Apache Flink that your application uses when you compile your application. You provide the version of Apache Flink with the -Dflink.version parameter as follows:

mvn package -Dflink.version=1.18.1

For building applications with older versions of Apache Flink, see Earlier versions.

Creating your Managed Service for Apache Flink application

Once you have built your application code, you do the following to create your Managed Service for Apache Flink application:

  • Upload your Application code: Upload your application code to an Amazon S3 bucket. You specify the S3 bucket name and object name of your application code when you create your application. For a tutorial that shows how to upload your application code, see Upload the Apache Flink streaming Java code in the Getting started (DataStream API) tutorial.

  • Create your Managed Service for Apache Flink application: Use one of the following methods to create your Managed Service for Apache Flink application:

    • Create your Managed Service for Apache Flink application using the AWS console: You can create and configure your application using the AWS console.

      When you create your application using the console, your application's dependent resources (such as CloudWatch Logs streams, IAM roles, and IAM policies) are created for you.

      When you create your application using the console, you specify what version of Apache Flink your application uses by selecting it from the pull-down on the Managed Service for Apache Flink - Create application page.

      For a tutorial about how to use the console to create an application, see Create and run the application (Console) in the Getting started (DataStream API) tutorial.

    • Create your Managed Service for Apache Flink application using the AWS CLI: You can create and configure your application using the AWS CLI.

      When you create your application using the CLI, you must also create your application's dependent resources (such as CloudWatch Logs streams, IAM roles, and IAM policies) manually.

      When you create your application using the CLI, you specify what version of Apache Flink your application uses by using the RuntimeEnvironment parameter of the CreateApplication action.

      For a tutorial about how to use the CLI to create an application, see Create and run the Application (AWS CLI) in the Getting started (DataStream API) tutorial.

    Note

    You can change the RuntimeEnvironment of an existing application. To learn how, see In-place version upgrades for Apache Flink.

Starting your Managed Service for Apache Flink application

After you have built your application code, uploaded it to S3, and created your Managed Service for Apache Flink application, you then start your application. Starting a Managed Service for Apache Flink application typically takes several minutes.

Use one of the following methods to start your application:

  • Start your Managed Service for Apache Flink application using the AWS console: You can run your application by choosing Run on your application's page in the AWS console.

  • Start your Managed Service for Apache Flink application using the AWS API: You can run your application using the StartApplication action.

Verifying your Managed Service for Apache Flink application

You can verify that your application is working in the following ways:

  • Using CloudWatch Logs: You can use CloudWatch Logs and CloudWatch Logs Insights to verify that your application is running properly. For information about using CloudWatch Logs with your Managed Service for Apache Flink application, see Logging and monitoring.

  • Using CloudWatch Metrics: You can use CloudWatch Metrics to monitor your application's activity, or activity in the resources your application uses for input or output (such as Kinesis streams, Firehose streams, or Amazon S3 buckets.) For more information about CloudWatch metrics, see Working with Metrics in the Amazon CloudWatch User Guide.

  • Monitoring Output Locations: If your application writes output to a location (such as an Amazon S3 bucket or database), you can monitor that location for written data.