On the whole, this is the concept of Route53. Hope you have learned something new about Route53 from this post. Thank you for reading.

Apart from mapping the domain names to IP addresses, Route53 also does something called as Health checks. It checks whether the server is up and running properly without crashing or not by sending the requests to that server.

You need to do many things such as buying the domain name, searching for the hosting platform, maintaining DNS records and all other things. To avoid all these internal things, AWS came up with the concept of Route53, which gives you this DNS for your application.

Due to these reasons, we came to the conclusion of the domain name system because remembering the names of the websites would be easier than remembering the IP addresses. The typical procedure for creating the domain name on your own would be hectic.

2. There may be chances of frequently changing the IP address. There may be many reasons such as when the server on which your application is running crashes, you need to change from one server to another at this time, and there is a chance of a change in IP address.

This is how DNS will work. Why does this concept of DNS come into the picture? The DNS came into existence due to 2 main reasons. 1. It is not easy to always remember the IP address of the server on which it is running.

Basically, this DNS maps the website names with their IP addresses. When you type the website name in the browser, it checks whether anything is mapped for this domain name. If something is mapped it retrieves the IP address of that domain name or else it shows an error.

Many of us would know that the actual websites will run on servers and we can access it through the IP address of that server. But how do you get the websites when you type the website name with some extensions such as .com / .in / .org. It is through the DNS.

Firstly, let us know What is DNS?🤔 Domain Name System(DNS) is the phone book of the internet. In simple words, Something is maintained on servers that store the dictionary type of things that map the website names with their IP addresses.

AWS provides many services such as Compute service through EC2, and Kubernetes as a service through EKS, in a similar manner AWS provides Domain Name System(DNS) as a service through Route53. In this thread🧵, let us know about Route53 provided by AWS.

This demonstrates the process to access the application that is lying in the VPC.

This security group will check incoming requests and allow only those specified requests that we have configured in the security groups. After passing through this security group, we can access the application. On the whole, these many things are combined in a VPC.

Security group: For each EC2 instance there will be something called Security group which acts like a security guard for the EC2 instance. Here we can define which port can be accessible from the internet and which cannot.

That means in this route table, we will define how to access the private subnet and provide it to the load balancer and the request will go in the defined path which is present in the route table.

(cont.)this load balancer will forward the request from the public subnet to the private subnet by providing the path to the request. Route table: For each subnet, there is a route table. This route table is used to give the correct path to the load balancer.

Through the Internet gateway, anyone who is accessing the resources from the VPC can access the public subnet and the user enters the VPC. Load Balancer: It is the thing that forwards the request to a particular path. Since we have come to the public subnet,

Internet Gateway: Gateway is the thing through which we can enter into the VPC. If anyone wants to access the resource from the VPC, he can access it by entering it into the VPC through the Internet gateway only.

We can specify one subnet as 172.31.1.0/24 and another as 172.31.2.0/24. Now we will get 255 IP addresses for each project. Within subnets, there are two things public and private subnets. Public subnets are exposed to the internet and private is not exposed to the internet.

That means we can get a total of 255*255 = 65,025 IP addresses. Subnet: Using subnets, we can divide/split our IP addresses. Let's say we have 2 projects and want EC2 instances for them. We can divide the IP address range for these 2 projects using subnets.

IP address range: In general language, IP address range can be defined as the size of the VPC which means that the VPC can have some number of IP addresses. This IP address range can be from 0.0.0.0 to 255.255.255.255 for IPv4. In VPC default IP address range is 172.31.0.0/16