3. [SAA/DVA] Route 53 – Registering a Domain
Okay, so let’s open the Route 53 service, which is a scalable DNS management system. Okay, so as we can see, there’s only one hosted zone for me and one domain for me. That’s because I’ve already registered domain, but for you it should say zero hosted zones and zero domains. So let’s go on the left hand side into register domains. And as you can see here, I’ve already registered a domain called Stefanthettichercom. So this is something I’ve purchased in the past and something that if you want to follow this section with me, you will have to purchase your own domain. So it has to be a domain that doesn’t exist already. Okay, so I’ve purchased Stefancier. com, but let me restore a domain with you.
I will not go all the way with the domain purchase, but I can show you at least the steps. So first we need to choose a domain. For example, no one has this domain except Stefan. com. I’m pretty sure this is going to be available. Let’s check and yes, it is available. So here we see the domains and the price. So this is something that’s going to cost me $12 per year. Okay, so just so you know, if you go ahead with this, well, you can practice alongside with me, but it will cost you a little bit of money. If you want to remain within the free tier of AWS, you cannot go ahead with this section.
Just have to watch. Okay, so let’s add this to Cart and we’re going to register this domain for one year. You cannot do anything lower than that. Let’s click on next. And then you have to specify the contacts for your domain so you can say the contacts that you have. So I will let you fill that in. And if you have the option, please enable privacy protection. This is to make sure that your contact details are hidden for domains and therefore you’re not going to be spammed by some people. After you register a domain. Next you check your contact details which will look good. And then automatically you will be using Route 53 to manage your domain. Do you want to automatically renew it? Yes or no? It’s up to you if you want to keep it forever. And then do you accept the terms and conditions? The answer should be yes. And then you can complete your order.
So once this is done, you’re going to have the domain being registered. It can take maybe a few minutes, maybe a few hours, but then you should be good to go and the domain should be ready. And finally, from there, you can go into your hosted zones and you should see a new hosted zone for your domain name that you just purchased. And as you can see, the type will be public. It’s created by Route 53 directly. You should have two record counts.
And then in this hosted zone, if you click on it. You’re going to have the NS records and the SOA records. So to make it simple, the only one you should worry about is this one, or not worry about. But just look at so the NS tells you the name servers. It’s saying that okay for this domain name, Stefanother. com, then these servers are the authoritative answers. They can give you the values of whatever records we’re going to have in this table. So that’s it for registering a domain name. I hope you liked it. And I will see you in the next lecture to start creating some records.
4. [SAA/DVA] Route 53 – Creating our first records
So now let’s go ahead and create our first records in route 53. So I’m going to go into my hosted zone and in there I’m going to create some simple records. So let’s have a look. We’re going to create a record by clicking on here and in here I can just have a record name. So we want it to be Test Stefanotshirt. com, but you can enter anything you want here. This is how you would create your domain names. Now you have to specify the record record type. So you can see there’s a lot of record types in here, but for now we’ll keep it simple. We’ll keep it as an A record and which is to root an IPV four address into a domain name to an IPV four address. So the answer is going to be value is eleven 2344, which is just a value we want to have. And this is not an IP we own right now, but just to show you just a random value later on we’ll be routing to a real EC two instance.
Okay, TTL is time to live. We’ll leave it as 300 seconds right now and the routing policy will routing policy, we’ll have a look at it later on as well. We’ll leave everything as simple routing. Okay, so let’s go ahead and create this record. And now my record has been successfully created. So the idea is that if I go to test Safefonthair. com, it is going to ask my hosted zone what is the value of that? And the hosted zone could say, well, the value of it is eleven 2234. So if you try to do it with a web browser so if you take your web browser and you open it and you press Enter, this is not going to show you many things because right now we don’t have 112234. There’s probably no server that exists with that IP as well.
And if I try to just access this URL, it doesn’t work. Okay, so what we know is what is going on behind the scenes. And so for this, we’re going to type some command lines. Now you can be using your command line on your Windows laptop or your Mac, but because I want everyone to follow the same way as me, I’m going to show you how to do it using the Cloud Trail environment in AWS. So let me open the measurement console and then I’m going to click here to open Cloud Shell and Cloud Trail is going to allow me to do some commands using a standard Linux command line interface. Okay, but this is fine if you want to just do it with your own terminal on Windows or on Mac.
Okay, so my terminal is now ready and if you’re on Windows, the NS lookup command is going to work. If you’re on Mac, the Dig command is going to work as well. But as you can see, these commands are not found on my Cloud Shell. So I need to install them. So I do sudo. Yum. And then install minus Y and then bind minus Utils. And this is going to install both the Nslookup and the Dig command on my Cloud shell. So let’s clear the screen. And now let’s try to do Nslookup test stiffantecher. com. And as you can see, I get an answer, which is that Testifan teacher is going to eleven 2234, which is corresponding to what is happening right here, which is cool. And I personally like the Dig command a little bit more because I’m more familiar with it. But if you type Dig and then the URL that you have okay, and press Enter, you’re going to see that and have the wrong command.
So stefanvilleteacher. com so let’s clear the screen and then retype the command. Okay, what here we’re going to see is that we have the answer section and it says testifandache. com is an A record. And this is the value of the record. So I like it better because it shows you the TTL, as we’ll see later on, and also shows you the A record, the fact that it is an A record. Okay, so we have created our first Route 53 record, and we have been able to query it using a terminal, which is called obviously, loading it from a web page doesn’t work right now, but we’ll see how we can do it later on when we have a real server. So I hope you like this lecture and I will see you in the next lecture.
5. [SAA/DVA] Route 53 – EC2 Setup
Okay. So now let’s do a little bit of setup for EC Two and an application balancer before we go ahead and play again with route 53. So what I’m going to do is go into the EC Two console and I’m going to create three easy two instances around the world with different public IPS. So I’m going to launch an instance. Now we should know the process by now. So Amazon and X two of t two micro. I will configure the instance detail. And here for the user data, I’m going to enter the user data from here. So what this is going to do is that it’s going to create a web server again and it’s going to say hello from the host name, and it’s also going to get the Availability Zone as part of the web page because it’s going to say a hello. Well, from EU West one A, which gives us some information around where the instance is located.
So I’m going to paste this as text and then click on add storage, add tags, security groups and I’m going to create a new security group with SSH and Http on port 80 and then launch my instance. And I can say that if this is fine, proceed without a key pair, which is fine. So we have done one of these in the Frankfurt region. Now let’s go into another region. For example, let’s go into US East One and in there I’m going to do the same process. I’m going to launch an Amazon Linux Two image instance details. I’m going to have the same user data at storage at tags security group. I will create a new one.
I will add the Http rule we’re good. Then I will launch my instance and I will say proceed without a key pair. Launch my instance. I’m going a little bit faster now, but you should have the hang of it. And then let’s create one last instance. So for example in the Singapore region, so in AP Southeast One, I’m going to create one last instance. So Amazon next two t two micro again. And then I will have my user data, add storage tags, security groups, I will add Http review and launch launch and then I will proceed without a key pair. Okay? So we have three easy to instance. Now what I’m going to do is I’m going to just get the public IP of each EC Two instance and write it down in my notes so I can just identify them. So in here, I’m going to have this IP for AP southeast.
Two, one. Then the other easy two instance was in US East One. So we’re going to have a look for it. Here we go, the instances here I’m going to get the public IPV Four and then paste it here. And this is my US east. One instance. And then, lastly, I had an instance in EU Central one. Yes, it is here, and I’m going to again copy the IP. So here we go. My IP address in here, as well as EU Central One. So I have three easy two instances, and I’m going to do one last thing. I’m going to actually create an application load balancer in this region as well. And you will see why later. But let’s go ahead and create a load balancer. So we’ll create an application load balancer. I’ll call it Demo ALB Route, route 53 in three subnets. And then for security settings, I will create a new security group, which will allow traffic on port 80, which is good. And then we’ll have a new target group.
So demo TG Route 53. Of instances, I will reserve my targets. I will add this instance as my register targets, review, create. And then I will also get this DNS name right here in here, just so we can check. Okay, so let’s make sure that each of these instances is set up correctly. So if I take my instance from AP Southeast and I go to this URL, I get a hello world from this domain name in AP Southeast one B. So this is working. Then if I do the same for EU East One, I’ll get a good answer. So in AZ us east one.
So that’s perfect. Then if we do the one for EU Central One, let’s make sure it works. Yes. In EU central one C. This is perfect. And then my load answer, I don’t think we’ll be ready just yet. It’s not just regular set, but once the ALB will be ready, then I’ll be able to actually access this URL. Okay, so my ALB should be ready. And if I refresh this page yes, I get the correct hello world. Okay, so we’re good to go. My easy to setup is complete, and I will see you in the next lectures to practice more of Route 53.
