Menu
Hi I am new to AWS world.
1) I have domain name bought and registred 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 to 1)
QUESTIONS:
But will it be enough to bind 1) with public DNS from 2), what are the limitations?
In micro plan are DNS, and IP dynamic?
339
If you're deploying on AWS, then you should be using Route 53 for a couple of reasons: it uses IAM for authentication; it tightly integrates with EC2, S3, CloudFront, and more; and it has smart mechanisms for global failover and health checks.
If you need to manually join an EC2 instance to your domain, you must launch the instance in the proper Region and security group or subnet, then join the instance to the domain. To be able to connect remotely to these instances, you must have IP connectivity to the instances from the network you are connecting from.
Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. Route 53 connects user requests to internet applications running on AWS or on-premises.
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 (I use GoDaddy) 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.
86
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
