Private connectivity continued to be a major focus this year, with several new capabilities designed to help customers securely connect Cloud Gateways to upstream services — without exposing traffic to the public internet.
### **Private DNS for AWS and Google Cloud**
Dedicated Cloud Gateways now support:
- - **Private Hosted Zone association on AWS**
- - **Private DNS Zone association on Google Cloud**
This enables private DNS resolution between Kong-managed gateways and customer VPCs, allowing teams to route traffic to upstream services using internal domain names while maintaining strong network isolation.
### **VPC Peering on AWS and Google Cloud**
We also expanded private connectivity with **VPC Peering support** on both AWS and GCP.
- - On AWS, VPC Peering complements existing Transit Gateway support, giving customers more flexibility in how they design network topologies.
- - On GCP, VPC Peering enables low-latency, private connections between customer-hosted services and Kong-managed gateways—reducing egress costs and eliminating public exposure.
These options allow customers to choose the networking model that best fits their performance, security, and operational requirements.
### **AWS Resource Endpoints**
To further simplify secure connectivity on AWS, we introduced **AWS Resource Endpoints** for Dedicated Cloud Gateways.
This allows customers to expose multiple upstream services through a single, customer-controlled VPC endpoint—using one-way connectivity that eliminates bidirectional peering risks. Configuration can be managed directly in Konnect, via API, or with Terraform, making it easier to standardize and automate secure networking at scale.