Amazon AWS Certified Developer Associate – Route53 & DNS Part 2

2. Route53 – Register Your Domain Lab

Okay, so here I am in the AWS console and I’m going to go over to services and I’m going to go down to Networking and click on Route 53. Now if you haven’t used Route 53 before, you’re going to get this dashboard. Just go ahead and click on one of the get started nows. And we just need to go under Domains and click on Registered Domains. And in here we can either register a domain or we can transfer a domain name to Amazon. So I’m going to register a new domain. I’m just going to call it Hello Cloud Gurus. And we could get hellocloudgurus. com. If you want the cheapest domain name, go for click that’s. They’re normally about $7. So let’s have a look here. Click $7, see if you can find anything cheaper. But I had a quick look through the list and dot click was the cheapest.

Just for consistency. I’m just going to go for I just want to see if it’s actually available. So here we go. Hellocloud GURUS. COM is available. Price per year is $12. I’m going to add it to my cart. You can see over here my subtotal. And then it says, Monthly fees for DNS management. You just want to click that and have a look at the pricing. You can, and you can see the pricing in here. It’s going to be fifty cents per hosted zone. But then you’re going to have traffic flows, you’re going to have queries, and then all the different pricing, whether it’s latency based routing queries, geods queries, et cetera, and then health checks.

I’d budget around $2. 50 a month, but you can of course delete this once you’re done with the labs. So I’m back in my cart. I’m going to go ahead and hit continue. So in here you’ve got to fill in all your personal details. So your first name, your surname, the organization, your email address, telephone number, and then your address. And then you have this option here as to whether or not you want to hide your contact information or don’t hide it. So that’s completely up to you.

I’m just going to go ahead and fill all this in and then hit continue. So once you’ve gone ahead and hit continue, you can just click in here that you’ve read the terms and the conditions and you’ve agreed to them. Go ahead and hit complete purchase. And it really is that simple. So just note in here it says that if your email address needs to be verified, one of our registrar associates will send an email to the registrant contact where the domain registration is approved. So you might have to just double check your emails. Also note that domain registration might take up to three days to complete. So do bear that in mind. So let’s just click on Go to Domains and you can see here it says domain registration is in progress. So I’m just going to pause the video. Hopefully it won’t be three days. Hopefully it will only be a couple more minutes, but I’m going to pause the video here and wait for this domain name to be registered. Okay, so I have got my verification email and I’ve clicked on it and it just says now that my email address has been successfully verified. Okay, I’ve just got an email from Amazon. It was about 15 minutes after I registered my domain saying it was ready.

So I’m just going to hit the refresh button and hopefully this will say, yeah, there we go. So it’s now under my registered domains. So here it is. Hellocloudgurus. com, we’ve got the privacy protection enabled, and the expiration date is going to be February 6, 2018, and it will auto renew. And if we click up onto dashboard, you can actually see it’s already created a hosted zone for us. So go ahead and click in there and you’ll see your domain name.

And if you click on the domain name, you’ll see two things. You’ll see the NS records and you’ll see the start of authority record, and you always need NS records and start of authority for any hosted zone within route 53. So in the next lecture, what we’re going to do is we’re going to start creating record sets. We’re going to go through the different records that you can create, and then we’re going to start looking at different routing policies. So if you’ve got the time, join me in the next lecture. Thank you.

3. Setup Our EC2 Instances

Okay, so here I am. I’m logged into the AWS console, and I want you to take a note of which region you’re in. So I’m in the London region because I’m based out of London, and I want you to select the region that is.

4. Simple Routing Policy Lab

Okay, so here I am in the AWS console. We just go down to services and then we click on route 53. Under networking, we have our hosted zone created when we registered this domain name. So. Hello, cloud GURUS. COM. And if I click in there, we’ll be able to see the record set. And by default, you always have two record sets that are created. So you have your start of authority and then you have your name servers. And note that the name servers, if you look here at the different top level domains, we’ve got a net, we’ve got a, we’ve got A, we’ve got a Co UK. They’re always going to be different top level domain names. And the reason for that is redundancy.

So for some reason net goes down, it’s only going to affect this one name server. It’s not going to affect the nameserver, the. com name server, the Co UK name server. So this is a very simple record set. What we need to now do is link this DNS record to our EC two instances. And so what we’re going to do is we’re going to go in and create a record set. Now in here you can see that we’ve got the name, so we could have www dot and then Hellocloud GURUS. COM. But actually we’re going to just create a naked domain name to begin with and that’s called an alias record. So if you hover over, it says specify whether you want this record set to be an alias for an AWS resources.

An alias record is similar in some ways to a CNAME record set. One of the differences is that you can create an alias for the zone apex, and by that the zone apex, they just mean the naked domain name. The naked domain name is just there’s nothing in front of Hellocloud GURUS. COM, there’s no www, there’s no mail, hellocloud GURUS. COM, there’s no sales, hellocloud GURUS. COM. It’s literally, if you type this in, it will resolve to that domain name.

So we do want an alias in this case. And alias records are supported for DNS record types of both A records and Quadruple A records. Quadruple A records are IPV six now, so we’re going to say yes. And in here we’ve got the alias target. So if we click in here, we’ll be able to see our different elastic load balancers. So we’ve got my London elastic load balancer and my Sydney elastic load balancer. So I’m going to go ahead and just click on this one and I’m going to keep the routing policy as simple and I’m going to not evaluate the target health. I’m just going to go ahead and hit create. And so now basically it’s created here. The type is an A record. It’s actually just an alias and it’s pointing to the DNS name of my elastic load balancer. So every time somebody wants to go to Hellocloudgurus. com, that is going to point them to the DNS name. Of my elastic load balancer.

Remember that? Load balancers do not have IP four addresses as such. That’s all managed by Amazon. You can only resolve an elastic load balancer by going to its DNS name. And that comes up in all the exams all the time. So do you remember that? And there we go. So essentially what this is doing is it will resolve Hello Cloud Gurus to the two EC two instances that are behind my elastic load balancer.

And so now, let’s test this. So if I open up a new tab and I type in Hello Cloudgurus. com and hit Enter, there we go. I’ve hit London web server too, if I refresh this a couple of times. There we go. I’m hitting one and two, one and two, one and two. So it’s just basically, essentially the DNS is resolving to my elastic load balancer, which has two EC two instances behind it. The routing policy is simple, so it’s basically effectively a round robin, essentially. And there’s no intelligence built into it whatsoever. So in the next lab, we’re going to look at weighted routing policy. So if you’ve got the time, join me in the next lecture. Thank you.

• Category: Uncategorized