Related Articles

18 Comments

  1. 1

    pl ease

    Eline sağlık hocam. Alakasız bir soru olacak ama 3 boyutlu olan ECS Cluster ı nerede çizdiniz? 🙂

    Reply
    1. 1.1

      Onur SALK

      Teşekkürler. Çizim için cloudcraft.co

      Reply
  2. Pingback: AWS Week in Review – September 19, 2016 | MOBILENEWS.WORLD

  3. Pingback: AWS Week in Review – September 19, 2016 - Browser Zone

  4. 2

    Lukasz Dorosz

    Hi. Nice and very useful post. I will try and put hands on your configuration 🙂

    Reply
  5. 3

    Mario Medina

    Excelent guide! followed every step and it works like a charm! Thanks Onur

    Reply
  6. 4

    Vita

    Hi. I have a question. Is it possible to configure ALB and auto scaling the next way: there is a web application and it’s components organized like microservices, each of them is on different port. For example, we have 3 components: c1, c2 and c3. c1, c2 and c3 are in different target group and on different ports, with different path(like you have in your example). At first we have only one EC2 with all components running on it, but we need to add more if one of the components overloaded and instance run out of memory/cpu. How should i configure autoscale to scale them correctly? i mean, can i alert when c1 overloaded end EC2 run out of cpu and add one more EC2 instance? perhaps maybe, some how. Now we have two EC2 instances running: on first all containers and on second only c1. But when c2 is also overloaded, we don’t need to add another EC2 instance, we should run c2 on second EC2 instance(if c1 is not using all instance’s resources).
    I don’t now how should i configure ALB and autoscaling to have behaviour i’ve described: not to launch new EC2 instance for every overloaded microservice, but use existing one. Is it possible?

    Reply
    1. 4.1

      Vita

      Would really appreciate your response with any advice!

      Reply
    2. 4.2

      Onur SALK

      Hi Vita,
      Attaching target groups to ASG is available via AWS cli, check this please.

      Reply
  7. 5

    Karthik Keyan

    Best tutorial, even better than aws official tutorial. Thank you for your effort. the default path / worked for me but not the /blog path. i used only one instance. i ran two services. one container in the service use port 80 as container port and one container in another service use port 443 as container port. the services are running but when i checked the target in its group, it says no instance are healthy. it keeps failing and dynamic host port is continuosly alloted to it. help me please.

    Reply
    1. 5.1

      Onur SALK

      Hi Karthik,

      Thanks for your good feedback!
      Can it be a security group issue? Or an issue with target group routing? Did you configure your routing and selected HTTPS for your protocol?

      Reply
      1. 5.1.1

        Karthik Keyan

        instances are healthy. the default path is working absolutely fine. hitting the load balancer url can route the request to default path(the first container can run) but the rule created as /blog doesnt route to the second service(the container can run). i get 404 error.

        Reply
        1. 5.1.1.1

          Onur SALK

          If you contact me via my email, I’ll try to help you.

          Reply
          1. 5.1.1.1.1

            Karthik

            Tnx a lot. It worked.

  8. 6

    Kien Do

    How can you define your security group to allow ALB access dynamic port in EC2

    Reply
    1. 6.1

      Onur SALK

      Hi Kien,

      Dynamic port allocation is done on the host, so for the EC2, you only need to allow ports for your web application. like 5000 in the example.

      Reply

Leave a Reply to pl ease Cancel reply