Here and welcome back now into this, we will be discussing about the VPC and point services.
Now, let us go ahead and understand this with a simple case.
Now, in a lot of organizations, they make use of a service providers like DataDot neuralgic for which
the metrics are being sent.
So, for example, let's say that you have your own VPC.
So this VPC belongs to your organization and you have another VPC of a service provider.
Now, what you'll do from the set of two instances using certain matrix matrix can be CPU utilization,
it can be your application matrix and so on.
So you send that matrix from your organization towards the service provider and from the matrix that
the service provider receives.
They go ahead and they give you a nice little graph for which you can go ahead and investigate, as
well as inspect the overall latency or any other issues that are being fixed for your organization's
servers or applications.
So this is a simple architecture.
Now, one of the challenges with this type of architecture is that this matrix from the Ishita instance
in your PC is being sent to the AC2 instance in the Visio for service provider or the Internet.
And one of the feature requests with a lot of customers requesting is that since the easy to instance
of both the consumer and the service provider are within the environment itself, then instead of sending
it over the Internet, why not send it over the Internet later?
This will not only save you cost, but it is much more secure and the interconnection remains private.
Now, one of the approaches in which this can be achieved is with the help of Vecepia.
No experience is great.
But if a service provider has thousands of customers, vectoring is something that cannot be looked
upon.
Primarily because let's take an example of there are two consumers, your consumers and your consumer,
too.
Now, most of the consumers are using the same carriage, which is 172 31 zero zero 60.
So in such cases, the victim will not work at the service provider side because there can be hundreds
of consumers which are using the same carriage.
So this approach is not possible in case if a VPC building approach was possible, then the entire connection
was through the ADRIS private network only.
So in order to overcome this specific challenge, it has introduced a feature of the service VPC.
And so what will happen, this type of architecture, is that the easy to instant's would basically
make use of your interface point.
And from the indecorous same point, the traffic goes to the network load balancer and from the network
load balancer, it goes to the set of instances of a service provider.
So there are two important constructs here.
One is the consumer and second is the service provider.
So all the consumer needs to do is that the easy to answer needs to send traffic to the interface end
point.
And now all the service providers they have to do is they have to create a load balancer.
And this load balancer needs to be associated with a set of instances.
And this interface endpoint would automatically send the traffic to this network load balance.
And this sending of traffic that is happening is via the established private network.
It does not cross the Internet.
And this is the basic idea behind this service breaking point.
So let us do one thing.
Let me quickly give you a demo so that this can be better understood now for today's video.
I have to easy two instances that are running.
One is the consumer, which is the left hand side setu instance.
And second is the service provider, which is the right hand side, easy to instance.
Now we also have a network load balancer that is created which is associated with the service provider,
easy to install.
So if I quickly show you, let's go to the load balancer.
So you see, I already have a network load balance that is created, so the right hand side part is
already created and that traffic is automatically eroded.
Now, discussing about the left hand side with architecture, we already saw that you see two instances
created and we also have an interface endpoint creator.
So if Athelia clear, I have one interface endpoint that is created.
So now as soon as the easy instance sends the traffic to the interface endpoint interface, end point
automatically sends the traffic to the network load balancer or the service provider.
Now, before we do that, let me quickly show you what exactly the instance at the service provider
level is hosting.
So let's go to the instance level.
Let's open up the service provider instance.
Let's call it a public IP.
And if I paste within the browser, it is basically a simple aperture based based piece that is available.
All right.
So now let's do one thing.
Let's go to the consumer side instance and let's make a request to the breaking point and see on how
the traffic gets redirected.
I'll copy the consumer IP, let's connect to the instance and from here, let's go ahead and copy one
of the DNS name associated with the interface in point.
Let's do a call on their DNS name and as expected, you basically see the same page.
So this is the test page in an e-mail format.
And you see it is basically the Apache St.Petersburg.
Now, the question that comes is how does this network interface endpoint in a consumer?
VPC gets linked with the network load balancer in the service provider VPC, and that is through the
service VPN points.
Now, if I go to the endpoint services, Audur, you should see that we have one endpoint service that
is created and within the endpoint connection we have a week end point.
So this is basically the end point eighty.
Let's copy this up.
If we go to the endpoint here, you see this end point.
If I just pace this eight point eighty, you can see this is the interface endpoint.
So what we do is we go ahead and create an endpoint service.
And this endpoint service is basically associated with a network load balancer.
So the end endpoint service in this service provider site, this endpoint services associated with the
network load balancer in the service provider side.
Now we connect the interface endpoint to the endpoint services.
So this endpoint service is associated with the interface endpoint.
So any time a traffic is sent to the network interface endpoint, it automatically goes to this end
point service, which in turn is associated with the network load balancer and from the network load
balancer.
The traffic goes to the easy to install.
So this is how the service VPC endpoint based architecture works great.
So I hope with this you understood the basics of the BCA endpoint services and with this will conclude
today's video.