3

During migration on AWS, I created a new cluster on AWS and deployed several docker application with Fargate approach. During each update of task definition, new task is launched inside service and new public IP is assigned from AWS public IP pool

Is there any solution or instruction on how I can attach static IP adderes to the service tasks?

I saw similar question here How do I associate an Elastic IP with a Fargate container?

but still can't find any solution

user2105282
  • 724
  • 1
  • 12
  • 26
  • Can you please add some more detail to the context of your application? What type of workloads do you plan on running inside aws fargate? Depending on your workload, I would imagine you will find that your best would be to set up an application load balancer connected to your aws-fargate service. – Roy Kachouh Feb 23 '18 at 06:53

1 Answers1

2

see this answer

add application load balancer to your fargate service. service auto scaling is bettor approach to do this.

Sunil Shakya
  • 8,097
  • 2
  • 17
  • 20
  • The only problem is that ALB cost approximately the same price as Fargate task - so for one fargate task you actually have price*2 – user2105282 May 10 '18 at 10:16
  • Did you try network load balancer? Somehow I feel fargate has to mature. – rashidcmb Jun 08 '18 at 16:41
  • Load balancer is not a solution, because it changes its IP from time to time, not very often, for me it happens once per 2 months and we had some bugs because of that. – Sergei Aug 15 '19 at 19:33