1 Answer
- Newest
- Most votes
- Most comments
0
I'm not sure how to route to a particular fargate task. However, I think you can route to different fargate services based on incoming route paths in Application Load Balancer. You can create a ALB with different listeners along with its associated targets. Then, when you're creating fargate service, you can attach this load balancer.
You can refer this article - https://aws.amazon.com/blogs/containers/using-aws-application-load-balancer-path-based-routing-to-combine-amazon-ecs-launch-types/
answered 2 years ago
Relevant content
- Accepted Answerasked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- How can I troubleshoot issues when I use the AWS Load Balancer Controller to create a load balancer?AWS OFFICIALUpdated a year ago
Hello, I don't believe AWS ALBs and Fargate currently support this functionality. However, you could try to add the target manually to the target group by public or private IP and remove other targets from your group. Alternatively, you could create a second service with only one running task and set up a separate load balancer for it.
If you provide more details as to why you only want to route to one specific task, I may be able to brainstorm alternative solutions.
Hi, Currently I'm planning to deploy a scalable session based websocket server on AWS using Fargate, each user will assigned a room automatically once they request to join and their message transmission should be encrypted(SSL). I plan to do the SSL part on the load balancer and hoping to do as what you said for the address routing.