We’re excited to introduce Private Endpoint Service for GrapheneDB — a new way to connect to your databases securely and privately within your cloud environment.
With this feature, you can now access your GrapheneDB databases over AWS PrivateLink, eliminating exposure to the public internet and giving you tighter control over network access.
What is AWS PrivateLink?
AWS PrivateLink is a networking service that allows you to access services privately within your VPC, without exposing traffic to the public internet.
Instead of routing requests over public endpoints, PrivateLink creates a direct connection between your VPC and the service through a VPC interface endpoint. This keeps all traffic within the AWS network, improving both security and reliability.
With PrivateLink, you can securely consume services without needing VPC peering, NAT gateways, or complex routing configurations.
If you want it slightly more technical (or more beginner-friendly), I can adjust the tone either way.
An Alternative to VPC Peering
Private Endpoint Service complements our existing VPC peering support. While peering remains a powerful and flexible option, PrivateLink offers a simpler and more isolated connectivity model.
With Private Endpoint Service:
- You don’t need to manage overlapping CIDR ranges
- Connectivity is scoped to specific endpoints instead of entire networks
- You can adopt a more granular, service-oriented network design
This gives you the flexibility to choose the approach that best fits your infrastructure and security requirements.
Pricing
Private Endpoint Service is billed per environment, not per database.
This means that once enabled, you can connect all databases within the same environment through the private endpoint at no additional cost per database or replica.
Keep in mind that standard AWS PrivateLink charges (such as interface endpoint costs and data processing fees) still apply on the AWS side.
Getting Started
Setting up Private Endpoint Service is straightforward, but it does require some AWS configuration (VPC endpoints, security groups, and port rules).
We’ve put together a step-by-step guide to walk you through the process:
👉 Read the full documentation:
https://graphenedb.com/doc/guides/environments/private-endpoint-service/
What’s Next?
This is another step toward giving you more control over how your data is accessed and secured. Whether you choose VPC peering or Private Endpoint Service, you now have more flexibility to design your network the way you want.
If you have feedback or questions, we’d love to hear from you.