- Newest
- Most votes
- Most comments
Hello.
Does this mean that the website cannot be displayed with the public IP address of EC2?
In that case, please confirm that a route to the Internet gateway is set in the route table of the subnet where EC2 is running.
Also, make sure that the network ACL of the subnet where EC2 is running allows all communication.
Make sure port 80 is allowed in the EC2 security group's inbound rules.
I think the problem is on my DNS. I've noticed only now that integrations.domain.pt is resolving to 123.123.123.123, instead of 345.3435.345.345 I think i need need you to update my DNS, so that both integrations.domain.pt and *.integrations.domain.pt resolve to the AWS EC2 public IP (345.3435.345.345)
My problem nopw is that I am new to AWS and am unclear if this is done on teh Windows Server or the AWS instance.
Would you have any suggestion?
Since this seems like a problem on DNS records, it needs to be done there. If you are using AWS Route53 as your DNS, then you can check if the record is correctly set to the EC2 public IP. If you are using another provider for the DNS, you need to do the same steps there. Based on the info provided above, I don't think any changes are required to your Windows server for DNS purposes.
Relevant content
- asked 5 years ago
- asked 14 days ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
In addition to this, please also make sure your windows firewall is not blocking inbound connections and folder permission (where the website files are) is set to everyone.