Hi, everyone, and welcome back.
Now, in today's video, we are going to look into the steps involved in creation of a Route 53 resolver,
inbound endpoints.
Now, the overall steps are very simple.
However, for testing, you can deploy an architecture something similar to the diagram that we have
seen, where you have a private hosted zone associated with the VPC one.
And there is a peering between VPC one and VPC two in place.
And if Route 53 resolver inbound endpoints are working, then the VPC number two should be able to resolve
the domains of this private hosted zone through the resolver endpoint IP addresses.
Great.
So at this stage I already have a private hosted zone that is in place called S Demo Dot Internal,
and this hosted zone in turn is associated with one of our VPC.
So let's go ahead and quickly create a inbound endpoints.
The creation step is very simple.
Let's go ahead and give it a name.
I'll just say inbound endpoint.
I'll select the VPC where the inbound endpoint is created.
So we'll be selecting the same VPC, which is associated with a private hosted zone and the same VPC
that has a P adding to the VPC number two.
All right.
The next important part is the security group of the endpoint.
Note that this endpoint has an IP address so you can restrict who can connect to this via the security
group.
Apart from that, you can also select the availability zone in which it would be created.
Let me just select one for simplicity.
Once you have done that, you can create an endpoint.
So at this stage, the endpoint creation is in process.
It takes a few minutes for the overall creation to be completed.
So let's quickly wait for a moment here.
All right.
So our inbound endpoint is now ready.
Now, if you'll quickly open up the inbound endpoints, you will see that there are two set of IP addresses
that are associated with this endpoint.
So whenever you want to make a query from on premise or appear VPC, you send a query to the IP address
of the resolver endpoint and things would work perfectly well.
Also, one more thing that you will have to verify is the security group to ensure that the requests
are not blocked at a firewall level.
Let me also quickly show you the security group now in the security group associated with the endpoint,
I have one rule of type UDP.
So the protocol here is UDP and the port is 53 and the source is one 7230 100 16, which is nothing
but the IP address of the VPC number two.
All right, so all the DNS queries from the VPC number two towards the resolver endpoint over here will
be allowed at the firewall level.
Now, to test if everything is working within our hosted zone, let me in fact create a new record here.
I'll just quickly create a record.
I'll just call it as zero two.
And the IP address is 192 168 0.100.
And I'll quickly create a record.
Now from the SC to instance of the VPC, if I'll quickly do a NSS lookup on 02. demo dot internal,
let's quickly verify if the resolution is working and at this stage the resolution is not working.
You can also try to send a query to the VPC number one plus to address.
So let's say 1077 0.2.
This is the plus two of the VPC number one.
Now at this stage you see we are not really getting a reply back and soon it will get a connection time.
Let's do a control C just to save time.
And instead of this, let's add the IP address of the inbound endpoint.
So let's go ahead and quickly copy the address.
Which is 1077 10.49.
So let's say 10.77 or 10.49.
And at this stage you see the overall name resolution is working perfectly well.
Great.
So I hope with this at a high level overview, you understood the basics about the inbound endpoint.
Again, you will see that the overall creation step is very simple and there is no complexity that is
involved here.
So with this will conclude today's video.