Do i need Amazon Route53 to bind domain to EC2

Question

I have a situation

1) I have domain name bought and registered by some third party (not amazon), where I set DNS values

2) I have EC2 micro instance and in panel I can find Public DNS, and Public IP

3) I have also route53 service with A record binding to IP from 2).

I copied dns values from Delegation Set in route53. But will it be enough to bind with public DNS from, if so what are the limitations?

Answer 1

You need to assign an Elastic IP to your instance and use that IP to configure the DNS A-record. An Elastic IP is the EC2 equivalent of a static IP. I don't think there is any additional cost to it as long as you don't leave an Elastic IP unassigned.

Once you have your Elastic IP, you can use the DNS tool of your domain registrar to bind the domain to your IP. You don't need Route53 to do that, but you can configure Route53 to replace your registrar's DNS servers if you prefer. For a simple setup with only one or two servers, I don't see much benefit in using Route53.