Support Apache Flink runtime for Kinesis Analytics

[parismorali]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

At the moment it is not possible to provision a Kinesis Analytics application based on Apache Flink java app.
It would be great if TF provided an option to allow this setup.

New or Affected Resource(s)

Presumably this would be implemented as an extension of aws_kinesis_analytics_application

• aws_kinesis_analytics_application

Potential Terraform Configuration

resource "aws_kinesis_analytics_application" "test_application" {
  name = "kinesis-analytics-application-test"
  runtime= "flink-1.6"

  s3_bucket = "my-jars-bucket"
  s3_object = "my-flink-app.jar"
}

References

[ziggythehamster]

I think the proposed configuration will have to end up also having a few more sections (CloudFormation reference):

property_group {
  id = "something"

  properties {
    key = "value"
  }
}

flink_application_configuration {
  checkpoint_configuration {
  }
  parallelism_configuration {
  }
}

Probably more. They structured this in a goofy way.

[jurgenweber]

this would be very handy to have in the provider, anything we can do to push it along?

[efeller]

+1

[ghost]

This has been released in version 3.12.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!