Hi, Adrian, and welcome back.
Now, in today's video, we are going to go ahead and look into the steps involved in creation of outbound
endpoints.
Now, do note that for outbound endpoints related lab, you will need a DNS server that is ready so
that the outbound endpoint can forward the query to the DNS server and it also receives the request.
So configuring the DNS server from scratch is something that we are not going to look into it.
I already have a DNS server in place in an account number two and there is a peering that is already
established.
So our main aim is to understand on how the outbound endpoint gets created and how you can create a
forwarding rule so that the overall setup can be completed.
Now for today's video, I have an easy to instance in the account number one.
The name is Account hyphen one, Easy two, and I also have a custom DNS server that is running in the
another account and there is a peering between both of them.
Now at this stage from the account number one ec two if I do an NSS lookup on FTP dot dot internal at
this stage you see it is not resolvable primarily because there is no outbound endpoints that is set
up.
However, if I send this query to the custom DNS server, let's try it out so I'll copy the IP of the
custom DNS server and if I send the query directly to that, you see it is working.
However, this is something that we do not want what we want that the query should go to the root 53
resolver associated with the VPC and this Route 53 resolver using the outbound endpoint, it sends it
to the appropriate custom DNS server, face the query and send the response back.
So in order to achieve this, let's go ahead and quickly create an outbound endpoint here.
I'll create outbound endpoint, I'll say demo, outbound endpoint.
You can associate it with the appropriate VPC.
So let me just select the appropriate VPC.
You'll also have to add a security group.
Let's select a security group and you can select the availability zone and the subnet configuration.
All right.
And you can create the outbound endpoint now at a high level overview.
You will see that the configuration of inbound and outbound endpoints are very similar.
However, at the outbound endpoint level, you'll also have to create a rules.
So let's quickly wait for a moment here.
All right.
So it took around 3 to 4 minutes and our Route 53 outbound endpoints are now ready.
Now, in order to test it out, if we do a NSS lookup on the CP labs dot internal domain as expected,
we are not really getting any reply back, primarily because at this stage the outbound endpoint does
not really know.
On if the query of KP Labs that internal is made to which server the query needs to be forwarded to.
And this is the reason why you need to create a certain set of rules.
So let's go ahead and quickly create it.
I'll say outbound rule.
The rule type here would be forward the domain name.
I'll say KP Labs dot internal, the VPC.
I'll just select the appropriate VPC.
And we'll also have to select the outbound endpoint.
And the next important configuration is the target IP address.
This is the address associated with the DNS server.
So let me copy the IP address of our custom DNS server.
I'll add it over here and I'll click on submit.
So our rule is created now within the outbound endpoints.
If you look, we have this outbound rule that you can see over here now from our EC two instance, if
everything is working, if you do an NSS lookup this time, you see we are getting the IP address back.
So as a client the benefit of outbound endpoint is you do not really need to worry about the IP address
of the custom DNS server today.
The IP address might be static one, but maybe tomorrow during migration, the IP address will change.
And if you have thousands of EC two instances, you do not really want to update the IP address of a
new set of DNS server in all of them.
So that is more problematic.
Instead, just configure the IP address of your custom DNS server as part of the outbound endpoints
and all the EC.
Two instances as part of your VPC will be able to take benefit of it without having to configure the
custom DNS server IP address in its configuration grid.
So I hope with this you understood the basics.
Now, again, one last thing before we conclude.
When we compare the inbound and the outbound endpoints in the inbound endpoint, we had to send the
query to the IP address.
So the servers that were part of on premise had to send query to the inbound endpoints, IP address
for the domain to be resolvable.
However, for outbound endpoint, you do not really need to worry about that.
Even though there are two IP address, you do not have to send the query to the set of addresses.
The default VPC plus two address is sufficient enough, which is part of the result.
Conf of the easy two instances, everything is taken care of by the resolver.
So that's the overview and with this will conclude today's video.