Problem with connecting frontend and backend services through internal load balancer

0 votes

I'm new to deploying web applications on AWS, but my co-workers are unable to solve the problem so if anyone can help with our problem, it'd be great.

Frontend and backend service seem to be working fine separately on its own, but when I try to communicate between frontend and backend I keep getting ERR_NAME_NOT_RESOLVED error.

  • Service discovery are all connected
  • All security groups are open

my AWS architecture

I think our architecture is very similar to this if that helps. (https://mohamedwaelbenismail.medium.com/microservices-architecture-deployed-on-ecs-fargate-based-cluster-using-cloudformation-878cb6f90571)

  • It only works if we change the internal load balancer to public load balancer allow internet traffic and allow 0.0.0.0/0.
  • Status of health check are all 'healthy'
Feb 16 in AWS by Ashwini
• 4,070 points
56 views

No answer to this question. Be the first to respond.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.

Related Questions In AWS

0 votes
1 answer
0 votes
1 answer
0 votes
1 answer

Does it make sense to have an Amazon Elastic Load Balancer with just one EC2 instance?

Well you are right Elastic Load Balancer is mainly ...READ MORE

answered Mar 20, 2019 in AWS by ArchanaNagur
• 2,360 points
315 views
+5 votes
7 answers

Docker swarm vs kubernetes

Swarm is easy handling while kn8 is ...READ MORE

answered Aug 27, 2018 in Docker by Mahesh Ajmeria
2,310 views
+2 votes
1 answer

Deploy Docker Containers from Docker Cloud

To solve this problem, I followed advice ...READ MORE

answered Sep 3, 2018 in AWS by Priyaj
• 58,100 points
2,071 views
webinar REGISTER FOR FREE WEBINAR X
REGISTER NOW
webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP