Introduction to AWS and Azure PrivateLink Services

Prev Next

PrivateLink provides a secure communication method between Unqork and an organization's resources by keeping traffic on a private network. Unqork integrates with two PrivateLink services: AWS PrivateLink and Azure Private Link. While both services perform the same function, they use different terminology and technology to do so.

For simplicity, AWS PrivateLink and Azure Private Link are referred to as PrivateLink in this article.

AWS and Azure PrivateLink offer the following benefits:

  • Enhanced  Security: Removes attack vectors to the public internet by eliminating public endpoints to services.

  • Private Cloud Connectivity: Provides a secure communication method between Unqork and an organization's resources by preventing traffic from leaving the private network.

  • Improved Application Performance: Keeps communication in the same region and the cloud provider's private network.

AWS and Azure PrivateLink both establish private connections between an organization's resources and cloud services. The patterns each service uses are similar, but the underlying technology differs. Each service uses unique methods and terminology to achieve the same result.

The table below maps equivalent AWS and Azure terminology.

Amazon Web Services Terminology

Azure Terminology

Description

AWS PrivateLink

Azure Private Link

Establishes private, stable, and secure connections between VPCs (virtual private clouds) and Unqork services.

VPC Endpoint Policy

Service Endpoint Policy

Dictates endpoint permissions for a service's API calls.

ENI (Elastic Network Interface)

Private Endpoint

A network interface that uses a private IP address from the virtual network to connect to AWS or Azure.

NLB (Network Load Balancer)

Load Balancer

Distributes incoming network traffic across multiple targets. Monitors target health and routes traffic to healthy targets only.

VPC (Virtual Private Cloud) Peering

VNet (Virtual Network) Peering

A private network that provides access to AWS or Azure resources.

Direct Connect

ExpressRoute

Creates private connections between AWS or Azure data centers and corporate data centers.

AWS and Azure PrivateLink patterns are used when private connections are required for Unqork to consume a private service without a public interface.

AWS PrivateLink:

AWS PrivateLink pattern: a private connection between a customer VPC and Unqork services using an Elastic Network Interface and Network Load Balancer. 

Azure PrivateLink:

   Azure Private Link pattern: a private connection between a customer virtual network and Unqork services using a Private Endpoint and Standard Load Balancer.

The AWS VPC and Azure  patterns extend PrivateLink to let Unqork consume a private service in a different region. Use peering when capacity limits or regional constraints prevent alignment on a single region footprint.

AWS PrivateLink with VPC Peering:

AWS PrivateLink with VPC Peering: extends private connectivity across regions using VPC Peering alongside the standard PrivateLink pattern.   

Azure PrivateLink with VNet:

 Azure Private Link with VNet Peering: extends private connectivity across regions using Virtual Network Peering alongside the standard Private Link pattern.

The AWS Direct Connect and Azure ExpressRoute patterns are used when Unqork must consume a service on a corporate network or data center.

AWS PrivateLink with Direct Connect:

AWS PrivateLink with Direct Connect: extends private connectivity to corporate data centers using AWS Direct Connect alongside the standard PrivateLink pattern.

   Azure Private Link with ExpressRoute: extends private connectivity to corporate data centers using Azure ExpressRoute alongside the standard Private Link pattern.

Combined Patterns

All three patterns from each service can be combined to connect Unqork to services anywhere in the world.

AWS PrivateLink with VPC Peering and Direct Connect:

AWS PrivateLink combined pattern: uses VPC Peering and Direct Connect together to connect Unqork to services across regions and corporate data centers.  

Azure PrivateLink with Express Route:

  Azure Private Link combined pattern: uses VNet Peering and ExpressRoute together to connect Unqork to services across regions and corporate data centers.

Frequently Asked Questions

Yes. Multiple services can run behind a single private API gateway. This is a common pattern that reduces the number of PrivateLinks and security policies to manage.

No. End-user traffic and traffic initiated by third parties goes over the public internet.

Yes. There are minimal costs for PrivateLink services and network data transfers.

Are there performance limitations on connections, bandwidth, or transactions per second?

Performance depends on many factors that must be tested and measured for each deployment. In general, private connections perform better than connections that traverse the public internet.

Yes, though some environments might require migration to the Kubernetes-based architecture. Contact a Customer Success Manager to learn more.


Changelog

Date

Change

2026-09-21

Imported and updated for UnqorkAI documentation.