Here you are.
And welcome back.
And now in two days, we will be discussing about one of the very interesting topics that is we talking
points.
Now, before we go ahead and discuss more in detail about the Ripkin points, let's take a simple use
case where a communication is required between a U.S. two instance and three.
Now, we already know that for the U.S. to intend to be able to communicate with various public services
like a Dinamo Debian and others, their traffic ultimately needs to be passed via the Internet and that
happens via the Internet.
So the traffic goes through the Internet to reach the public as re-import.
So if you look into it in architectural perspective, the two instances that are available, let's assume
it is in a public subnet, the traffic facilities, the Internet gateway from the Internet gateway to
is to the east, Republican point towards the S3 bucket.
And this is all good.
However, there are certain challenges that are introduced specifically whenever the workloads are private.
Let's assume that you have a private subnet where you have created a two instance.
Now, this is two instance wants to communicate with the S3 market.
Now, since there is no direct route that is available via the Internet gateway, the easy to instance
will not be able to do a communication ministry.
Now, one of the questions that comes is why don't you directly put a navigator in and then the communication
can go via the market.
So this is good.
But many times in a lot of organizations, the workloads are very sensitive.
So they host very sensitive data.
And auditors typically recommend that the easy two instances should not be able to communicate to us
the Internet directly or indirectly.
So in such cases, the challenge becomes that the easy to influence will not be able to communicate
with the established services as well.
So this is one of the challenges that many of the organization they face now.
Also some of the downsides, specifically whenever you're making use of a public Internet.
First one is that there are data transfer costs that are involved, say that you are uploading as well
as downloading terabytes of data from easy to three or vice versa, then you'll have to also pay for
the data transfer costs, also be a higher latency specifically of the large amount of data travel to
the Internet.
It can also bottleneck your Internet gateways, specifically when you have large amount of data that
is being uploaded or downloaded and also you have a security reasons as of it.
Now, in order to overcome these challenges, Edwards has introduced a feature called VPC Points.
So at a high level overview, VPN points allows us to connect VPC to another A.W. services or to other
support services or a private network.
And this is a big advantage.
So now let's say, for instance, in a private subnet, who wants to communicate with these three?
Assuming that you do not really have an A.N. even Internet gateway with the help of a webcam in this
instance will be able to perfectly communicate to the S3 bucket.
So instead of the Internet gateway, now you have the VPN point and this entire network communication
that we are discussing, it goes to the established private network.
It does not go towards the Internet.
And this is the high level overview about the benefits of visiting visiting.
So before we conclude, let's go ahead and have a quick demo associated with the VPC endpoints.
Now for today's demo, I have to see two instances that are available.
One is in the public subnet and second is in the private subnet.
This is very similar to the diagram that we are discussing.
You have easy to send in public and you have an easy to instance in private, not the easy to influence
in public subnet has a direct route towards the Internet gateway and the easy to instantaneous private
subnet does not have any associated drought with the Internet gateway.
Now, let me also show you this.
So we have this VPC and within this VPC.
So within a year there are two subnets that are available.
One is the public subnet.
As we already know.
If we look into the round table, one of the round goes towards directly the Internet gateway.
And if we explore the private subnet, you see, it does not have any doubt to us in then institutionality.
So you just have a local road that is available.
So let's do one thing.
What we'll do is will go ahead and connect to the private AC2 instance here.
Now, since this private Ishita instance does not have any Internet route, we cannot directly connected
to it.
So what we do will first connect to the public, to and from the public as it will go, then connect
to the private Isleta instance.
So let's do one thing.
Let's go ahead and quickly connect to the public.
Easy to instantiate.
So the first exercise that we are doing is towards the public to.
Let's quickly go to the road user and now we'll go ahead and connect to the two instance in a private
subnet and we are connecting the other private IP.
So let's go ahead and connected.
And as expected, things are working now from this private easy to effectively do it as trialist.
I'll also specify region.
Let's say up north is three.
As expected, you will not see any reason, primarily because there is no way of routing this specific
traffic towards this trip.
So now I also have the in point that is already created.
Let's go ahead and associate this end point with the roundtable, which is associated with a private
submarine.
So let me go ahead and do that.
So now from the easy doing this, let's go ahead and run the test results.
Come on.
Yet again.
And now you see things are working perfectly well.
Now, this traffic that we were discussing, this traffic is going the other VPC end point.
So let me also show you this within the subnet of private subnet here fairly quickly go to the round
table here, apart from one of the roads that was present.
You also have one more with that target of VPC in point.
So now automatically, whenever the traffic from the easy to instance, when it is destined to go towards
the S3, you UARS, the traffic will be routing via this specific route.
So this road is where the traffic will be routing to and it will be the there to the webcam point through
which the communication happens to the S3 market.
Great.
So I hope at a high level overview you understand the basics of the point.
Not only it helps us in the data transfer cost, it gives us the lower latency that is no longer a bottleneck
at the Internet gateway.
And you also have a better security.
Now, one of the questions that comes is why are better security?
Primarily because ultimately, even at the entry level, the traffic between the two and a three is
always encrypted.
So do not at a high level overview, even when we discuss about the EDP deal, is also has some vulnerabilities
that always are released after a certain amount of time.
So it is always better when it comes to sending the traffic over a private network rather than sending
over the Internet.
And this is one of the things that auditors are also happy about, specifically for the sensitive workload.
If you are sending the traffic or the private network, that's great.
So I hope that this you understood the basics of making points and will conclude today's video.