Member-only story
Part 3 — Interface Endpoints — Testing with S3 and Workspaces as services — Practically Illustrated for understanding
The very reason I made a choice to set up an IPSEC-Tunnel from another cloud provider will pay off in understanding this concept beautifully.
I have made a simple flow diagram to write down the article and also make it easy for anyone to replicate and test the service. I will try to make the video
Important Links:
What is an Interface Endpoint?
Interface End-point will allow you to connect to 100’s of various AWS services, marketplaces, and cross-account services owned by you privately. In Plain words, you do not have to go out of the AWS eco-system or touch AWS eco-systems public connectivity nodes and connect to AWS public services like S3, Kinesis, Dynamo, etc.
Technical terms like service-provider and service-consumer are referred to while creating an endpoint, that's nothing but who wants to request a service vs who offers their service, this plays an important role in understanding one critical component, Service-provider can never initiate a connection to service-consumer meaning, let's say your EC2 instance wants to connect to S3, EC2 can initiate outbound to S3 but S3 cant initiate the connection first (it won't any which way strictly speaking, but this applies to any private offering like a marketplace, other account services, etc, you get the idea) and reason for that is also simple, Private-link communications get NATed and hence it's completely fine even if your server and client have the same IP address as well.
I will create two interface endpoints, one S3 and one Workspace(PC Offering service), now the whole point of these endpoints is to get…
