The skeleton of the application has now been created. But you still need to adapt important configuration options, including the location of the Jar file on S3, the name of the Kinesis data stream to read from, and the Elasticsearch endpoint.
On the resulting page press the blue Configure button to configure the Kinesis Analytics application.
Enter the bucket and prefix of the compiled jar file under Amazon S3 bucket and Path to Amazon S3 object. You can obtain the correct values from the Output section of the CloudFormation template under FlinkApplicationJarBucket and FlinkApplicationJarObject.
Expand the Properties section and select Create group.
In the resulting dialog, choose
FlinkApplicationProperties as Group ID and add the following two key/value pairs and confirm with Save:
InputStreamNamewith the name of the Kinesis stream you’ve created earlier, eg,
ElasticsearchEndpointwith the Elasticsearch https endpoint you have noted earlier
Expand the Snapshots section and Disable snapshots for the application
Enabling snapshots allows the service to maintain the state of a Flink application in case of application updates but also when recovering from infrastructure or application errors. So for production environments it is highly desirable to keep snapshots enabled.
Expand the Monitoring section. Select Task as Monitoring metrics level and enable CloudWatch logging.
Keep the default settings for Scaling and VPC Connectivity and press the blue Update button at the bottom of the page to update the properties of the application