Here and welcome back again.
So in the last week, we were discussing about the basics of interfacing point, we also looked into
it in a demo perspective.
So in today's video, we'll go ahead and implement interfacing point and look into the steps that are
involved.
So going to the VPC management console, let's go to the endpoints here.
Now, in this, if you have a gateway point still running, you can go ahead and delete it so that the
unnecessary charge does not come.
However, today, for the time being, let's quickly focus on the interface and point here.
Now, as you're discussing that there are multiple services that are supported by the interface point
here.
The one that we are interested is easy do for today's video to keep things a little different, because
for the gateway endpoint, we had made use of the S3 service.
So to keep things different will be making use of the easy to service.
And the one that we are looking for is the first one, which is once the service is selected, the next
important thing is to select the availability zone with the interface endpoint would be created.
So basically this is a network interface as we're discussing.
So this network interface would be associated with which of the subnet is something that you can look
into just for simplicity, just let associated with all of the subnets.
Let's go big down.
And here you have the security group.
Let's leave it before the policy.
We leave it as default.
Lets go ahead and create the interface and also the interface endpoint is created.
Now, do know that it takes a little amount of time for the interface endpoint to be created.
So till that time.
Let's do one thing.
Let's go to the security group.
So there should be one security group that should be associated with the network interfaces and lets
go ahead and allow the webcam idea.
So under the inbound rules here, you currently only have the source of default.
Let's quickly changes and allow the Lepke idea here, which is 172 31 zero zero 16 or Les Gordon Cevdet.
That's correct.
So approximately after two to three minutes are interface, end point is up and running now within the
two incidents.
Let's go ahead and try it out.
So let me go then connect to the public.
Easy to know again, since this interesting point is associated with all of the subnets, it will work
perfectly well in the public as well as the priorities, the two instances.
So let me quickly, Gordon, connect to the public.
Easy to instantiate and let's do it from the second tab as well.
All right.
Let's switch to route and this very further.
TCP dump utilities available.
If you just run the DCP Dunkleman, you should see the packet capture.
Let's do a comprehensive alert.
Perfect.
So now from the first step, we go ahead and do it easy to describe instances and the region would be
us e one just for simplicity.
So this is a different region from where interfacing point is created.
If you think that it is fine, if you are getting an authorized operation, that is perfectly fine.
But the primary aim for this part is to verify to which end point of this connection is going to.
So it will quickly divert DCP dump on the destination port of four for three years.
Let's run the same command yet again.
Can you see it is going towards a public end point over here.
So now this thing, Lidstrom, the same gunman and this Jean the region to us to a stop where are easy
to instant's and the interfacing points.
So let's run that DCP packet captured yet again.
We are getting another operation that is fine.
And now you see that traffic is now directing to 172, 31, 33 to Dufay.
So this is nothing but an interface and point.
Along with this, you also have the EPA in point, which is easy to us, to a student Amazonia dot com.
So this should be directed towards the interfacing point.
Now for this from my workstation.
Let me go ahead and do an s lookup just to understand how things are working.
You see, it is directing to public IP audio Rolet so easy to use, which to me is only the dot com
is directing to a public IP.
Now the same thing.
If we do it from RTC to instance, you see it is being directed toward Interface Point IP.
So there are multiple IP addresses over interfacing points and this is where the traffic is redirected
to.
So this is a completely private connection with the live picture.
Now from a public issue to let me also go ahead and connect to a private Ishita instance, ending with
the IP of 30 dot 90.
So let's quickly verify.
So the priority is to appease 30 dot 90.
Now, since this private DC to IP does not have an Internet route, if we do it easy to describe instances,
let's specify a region of the US e one.
Now for this specific connection, you will not see any output.
So neither you will see the output, neither you will see any access denied message, primarily because
the EPA is not been able to complete.
You have this thing instead of us.
E one.
If you will just do a uSwitch two, you'll get access denied message primarily because the was successfully
made to the ITU.
But since the instance does not have appropriate and rule policy, you are getting a permission denied
message.
Great.
So I hope that this you understood at the high level your how the interfacing point works.
Now as we were discussing the interface endpoint basically enables us to use the security group to restrict
access to the endpoint.
So let's also try it out so that there is no confusion that arises at a later stage.
So what we'll do is we'll go ahead and allow only the IP address of our public to to connect to the
security group associated with the network interface of the interface endpoint.
So let's do one thing.
Let's go to the security group.
Let's modify the security group here and within the involvement will only allow, instead of the entire
Syeda will only allow the IP address of our public.
Isidor.
All right.
So now if you run this specific command, even this specific message that we were seeing should not
appear.
So let's try it out.
And as expected, now, you see you're not able to see anything, primarily because the traffic is denied
at the security group level.
Now, along with this, the interface endpoint point, it supports the access control board to the other
security group as well as policy.
So you can go ahead and create a policy based on which the access decision can also be made.
Great.
So I hope that this you understood the practical aspect of creating an interface endpoint and with this
will conclude today's video.