Virtual Service Endpoints for Low Latency VPC Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for accessing services in virtual private networks within provider networks often result in increased latency due to the need to traverse intermediate public networks, and private network peering has limitations on scalability and resource exposure.

Innovation Solution

Implementing service endpoints within customer private networks that allow direct communication with services in other virtual private networks through the provider network substrate without going through the intermediate public network, using virtual network interfaces and encapsulation protocols to route packets securely and efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If services are accessed through intermediate public networks, then network connectivity is achieved, but latency increases

Engineering Contradiction:
Improveaccess speedVSAvoidlatency
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent introduces service endpoints as intermediary components deployed within customer private networks. These endpoints act as local proxies that receive service requests from resources in the private network and forward them to the actual services in other virtual private networks. By placing this intermediary locally rather than routing through public networks, the patent eliminates the need for traffic to traverse external networks, thereby reducing latency while maintaining connectivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If private network peering is used to connect virtual private networks, then direct communication is enabled, but scalability is limited and resource exposure control becomes difficult

Engineering Contradiction:
ImprovescalabilityVSAvoidnetwork configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the network architecture by introducing service endpoints as independent, deployable components within each customer private network. Instead of creating complex peering relationships between entire networks, the solution breaks down connectivity into individual service-level interactions. Each service endpoint is a self-contained unit that can be independently provisioned, configured, and managed, allowing granular control over which services are accessible from which networks without requiring full network-to-network peering.

Inventive Principle:
Principle #1Segmentation

3Reliability

If service endpoints are deployed in customer private networks, then direct communication path is established, but network infrastructure complexity increases

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidendpoint deployment complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent employs virtualization to create virtual copies of network interfaces and endpoints that can be deployed within customer private networks. These virtual service endpoints are software-based representations that replicate the functionality needed for direct communication without requiring physical hardware modifications. The virtualization layer abstracts the complexity of endpoint deployment, allowing service endpoints to be instantiated as software components that can be managed through standard virtualization mechanisms rather than requiring complex physical network infrastructure changes.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3646175B1Virtual private network service endpoints
Publication Date: 2023.08.02 AMAZON TECH INC
  • EP3646175B1 patent drawingFigure 1A
  • EP3646175B1 patent drawingFigure 1B
  • EP3646175B1 patent drawingFigure 1C

AI summary

A customer may request a service endpoint for a service in their virtual network on a provider network. In response, a service endpoint is generated in the customer's virtual network, a local IP address in the IP address range of the customer's virtual network is assigned to the service endpoint, and a DNS name is assigned to the service endpoint. Resources on the customer's virtual network resolve the DNS name of the service endpoint to obtain the local IP address of the service endpoint and send service requests for the service to the local IP address of the service endpoint. The service endpoint adds routing information to the service requests and sends the service requests over the network substrate to be routed to the service.