- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
There's probably a couple of issues here - I suspect that as an instance reboots and becomes available, there's a short period whilst the network connection is simply unavailable.
I'm not entirely sure of your URL configuration but it might be that you're seeing issues with DNS propagation if you're updating Route53 with the new IP as the EC2 reboots. This would mean that for a short period as you access the URL, it could be pointing to the old IP address.
For the website, I'd consider placing a load balancer in front of the EC2 which will give you a consistent URL to IP mapping, but you still need to consider that if a single instance needs to be rebuilt/reboot you would have a period where the website wouldn't be available as health-checks etc. re-establish a healthy instance, so you might want to consider an auto-scaling group with two or more EC2 instances to provide high availability?
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Thank you so much for your answer. The issue was solved after chatting with an AWS support and generating an elastic IP. The newly generated IP was banned for some reason in our country and it was solved after having an elastic IP.