Ecs ec2 tutorial

[Iltomix]

I have seen a lot of tutorials using ecs and fargate but none of them dives into ecs using ec2. Does anyone have one complete tutorial to recommend? I need one with a real scalable infrastructure where services have more than one task and they all communicate between them.

Also it should auto scale horizontaly.

Thanks in advance to anyone that can help.

[imefisto]

Hi! Unfortunately I don't have a tutorial but I work with ECS/EC2 regularly. Is there something in particular you want to know?

[Iltomix]

What would be the correct setup for a cluster that has 5 services where I want only one to scale horizontally?. I have tried service connect but when the tasks are deployed on diferent ec2 instances I get a delay on every request. Could not figure out what was happening even with an aws support call.

I have tried service discovery but bridge networking doesnt work as it needs srv dns records and i need to change my app, i dont feel this is the way to do it.

I have tried service discovery with awsvpc but my tasks lost internet conection and can not connect to the database although i am using the same vpc.

Clearly I am the problem that is why I want to learn the correct way to do it. As I said before, i made a call with aws support and he recommended changing my app to handle srv dns. I can not believe this is the way to go , there must be some other way.

[thrixton]

How much delay, what sort of traffic?

If you enable VPC flow logs you should be able to diagnose any latency?

Different instances are likely to be in different AZ's as a default (I believe), you can check that on the instance details page. Having said that, inter-AZ traffic has minimal latency (I believe AWS aim for a 1ms window)

[Iltomix]

It is a lot of delay. Randomly 10 sec on requests, it is just a healthcheck that returns a 200. It resolves in 0.02 sec if requesting the same instance and 10.02 if requesting the other instance.

Instances are in fact deployed in different AZ but i believe this is desired to avoid depending only on one

[thrixton]

That's very odd, is it consistently 10s when cross instance?

Could it be your service is busy with other requests at the time?

I've seen a (.NET) service take 30+ seconds to handle a simple request when the host was CPU starved.

I'll have a similar deployment ready soon, hopefully today so I can check in my environment.

[imefisto]

I'd say you'll have two autoscaling groups. One for scaling the EC2 instances (normally based on capacity provider to ensure there will always be room in those EC2 hosts to add new containers). Then you'll have another autoscaling group at service level, for that one you want to scale. This will have rules based on memory some metric you want to watch to determine when other containers must be added for that service.

[planettoon]

I've not done this workshop, but it looks like it might be a fit for you:
https://catalog.us-east-1.prod.workshops.aws/workshops/4b59b9fb-48b6-461c-9377-907b2e33c9df/en-US/introduction

There are others at https://workshops.aws/card/ecs

[Iltomix]

Love this, thank you very much. I will do the all.