Why can’t I access my EC2 instance after removing the load balancer?

0
13
Asked By CuriousCoder92 On

I recently removed a Route 53 domain from my load balancer and pointed it directly to my EC2 server because the load balancer was no longer needed. However, now my site isn't resolving after making that change. What do I need to update beyond just the A record to get everything working again?

16 Answers

Answered By Dan On

a

Answered By TechWhiz42 On

Why not keep the load balancer? It helps with things like TLS certificates and better availability across multiple availability zones, even if you were only using one server. Did you make any changes to your instance's configuration?

CuriousCoder92 -

The load balancer was set up by consultants before I joined, but we never utilized it. We were paying for it without needing to. That's why I thought switching it off was okay.

Answered By On

c

Answered By On

C

Answered By On

N

Answered By On
Answered By On

c

Answered By On

N

Answered By On

a

Answered By On

a

Answered By On

C

Answered By Aaron Garnes On

{

Answered By On

c

Answered By On

c

Answered By ServerGuru88 On

It sounds like you might not be fully aware of what the load balancer was doing for you. Besides just routing traffic, it provided TLS offloading and basic security features. If your instances were set up behind the load balancer, they might not be directly accessible anymore, especially if they are in a private subnet with tight security rules. You should check if you're trying to access a private IP instead of a public one. That might be why you're having trouble reaching your site now.

Answered By On

a

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.