Help improve AWS Support Official channel in re:Post and share your experience - complete a quick three-question survey to earn a re:Post badge!
Reuse Load Balancer for multiple EMR Studio and Interactive endpoints
Is it possible to reuse a single Load Balancer when deploying multiple interactive endpoints that will be associated with different users using EMR Studio? Implementation is on Amazon EMR on EKS. Reference: https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/how-it-works.html
- Newest
- Most votes
- Most comments
Yes, it is possible to reuse a single Load Balancer when deploying multiple interactive endpoints for different users using EMR Studio on Amazon EMR on EKS. This can be achieved by leveraging the AWS Application Load Balancer (ALB) controller and configuring it to manage multiple endpoints.
The AWS Application Load Balancer controller is designed to manage Elastic Load Balancing for an Amazon EKS Kubernetes cluster. When you create interactive endpoints for EMR Studio, the ALB controller provisions an Application Load Balancer that exposes these endpoints outside the Amazon EKS cluster but within the same Amazon VPC.
To reuse a single Load Balancer for multiple interactive endpoints:
-
Install one AWS Application Load Balancer controller for your Amazon EKS cluster.
-
Create multiple interactive endpoints, each associated with different EMR Studio users or workspaces.
-
For each interactive endpoint, an Ingress resource will be automatically deployed. These Ingress resources will be managed by the same ALB controller.
-
Configure listener rules on the ALB to route traffic based on specific criteria, such as host headers or path patterns. This allows you to direct requests to the appropriate interactive endpoint based on the incoming request.
-
Use target groups to associate each interactive endpoint with the ALB. Each target group can correspond to a different EMR Studio workspace or user.
By following this approach, you can efficiently use a single Application Load Balancer to handle multiple interactive endpoints, reducing infrastructure complexity and cost while still maintaining isolation between different EMR Studio users or workspaces.
Remember to properly configure security groups and network access controls to ensure that each user can only access their designated interactive endpoint through the shared ALB.
Sources
Overview of interactive endpoints - Amazon EMR
Load Balancer for multiple sub-domains | AWS re:Post
How do I add multiple target groups to one Application Load Balancer using the Console | AWS re:Post
