if anyone wondering why service discovery with route 53 private hosted zone for SRV record didn't work, then please read this article: stackoverflow.com/questions/56897754/not-able-to-make-aws-ecs-services-communicate-over-service-discovery, as explained here the client itself has to support resolving capability of SRV record or you can use Nginx Upstream concept to achieve that. A record will work fine but then don't use ECS network Bridge mode, instead use AWSVPC mode.
You can plan your service container ordering if they are behind an ALB. So you can say that APP2 id dependent on APP1 and APP2 will start first and only then APP1 will start. Pretty handy at production.
Great, I have doubt,I am creating application load balancer for front end and creating service discovery for backend (number of user requests loads for front end are managed by application load balancer,so what about backend weather we need to create application load balancer separately or else that service discovery will act as load balancer for backend )
Bro, suppose if there are same 2 service running, then how to use A record? It the load balancer need to be added? Please make a video with auto scalling service and load balancer.
Hi, Thanks for the video. Can you share more details if you have figured out why SRV record was not working. I am seeing Unknown Host Exception in the container logs when I use the SRV record. Is there a different way of using a SRV Record?
Hello this is a great tutorial ... am wondering how you to connect Fargate Service Container to a Private EC2 instance(I think maybe I create Load Balancer and then call it inside the Container application). Any Ideas will be great 👍 Thank you
Thanks, I have spent days trying to connect Fargate containers with EC2 and finally understand that SRV was the problem.
if anyone wondering why service discovery with route 53 private hosted zone for SRV record didn't work, then please read this article: stackoverflow.com/questions/56897754/not-able-to-make-aws-ecs-services-communicate-over-service-discovery, as explained here the client itself has to support resolving capability of SRV record or you can use Nginx Upstream concept to achieve that. A record will work fine but then don't use ECS network Bridge mode, instead use AWSVPC mode.
OMG, you save me!! Thank you
You can plan your service container ordering if they are behind an ALB. So you can say that APP2 id dependent on APP1 and APP2 will start first and only then APP1 will start. Pretty handy at production.
Does anybody have any clue why discovery service option is no longer available while creating a service
Great, I have doubt,I am creating application load balancer for front end and creating service discovery for backend (number of user requests loads for front end are managed by application load balancer,so what about backend weather we need to create application load balancer separately or else that service discovery will act as load balancer for backend )
Excellent video! ECS networking is a very important topic for cluster design! PD: Your English is ok, don't pay attention to the others comments :)
Bro, suppose if there are same 2 service running, then how to use A record? It the load balancer need to be added?
Please make a video with auto scalling service and load balancer.
Hi,
Thanks for the video. Can you share more details if you have figured out why SRV record was not working. I am seeing Unknown Host Exception in the container logs when I use the SRV record. Is there a different way of using a SRV Record?
You can try to use your service discover name like ( local.backend.com) , so that it will work fine.
Can you share the code please ???
this could have been explained in less than half an hr 😑
you need more practice. Thanks for stackoverflow solution
You need to improve your engish! Thanks for the video.
Hello this is a great tutorial ... am wondering how you to connect Fargate Service Container to a Private EC2 instance(I think maybe I create Load Balancer and then call it inside the Container application).
Any Ideas will be great 👍 Thank you