aws / aws/containers-roadmap

[EMR on EKS] [request]: Flink support for EMR on EKS

Open
#1,761 4 comments 30 reactions 0 assignees View on GitHub
EKS EMR Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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

**Tell us about your request**

We would love to be able to use EMR on EKS to use [Apache Flink](https://flink.apache.org/).

**Which service(s) is this request for?**
EMRContainers / EMR on EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

We are trying to use Flink to process data streams in our data mesh architecture.

**Are you currently working around this issue?**

We are using the [Apache Flink Operator](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/). However since we are also using EMR on EKS for Spark jobs, we would love to be able to only have a single solution to solve both of these needs.

**Additional context**

EMR already supports Apache Flink.

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the EMRContainers / EMR on EKS service context and the linked Apache Flink and Flink Kubernetes Operator references. Define what Flink support alongside Spark would include and how completion would be verified; the issue does not identify repository files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, stream-processing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.