Edmund AI Documentation
/SETUP GUIDES

Overview

What the PrivateLink connection does, who builds which part, and what each side hands over.

Edmund reads a database in the customer’s AWS account through AWS PrivateLink. The customer publishes one database port as an endpoint service. Edmund connects to it from its own AWS network.

Traffic stays inside AWS. The two networks are never joined, so their address ranges may overlap. Edmund reaches only the published port, and connections can be opened only from Edmund’s side.

For a database outside AWS, use the Site-to-Site VPN.

Edmund's endpoint connects over PrivateLink to the customer's load balancer in front of the database

Scope of this document

PartCoversDone
OverviewResponsibilities, the exchange between the two sides, security—
SetupLoad balancer, endpoint service, database user, accepting the connection — with example values and commandsOnce, by the customer’s AWS administrators

Division of responsibility

TaskCustomerEdmund
Send the AWS account ID and region●
Build the load balancer in front of the database●
Create the endpoint service and allow Edmund’s account●
Create a read-only database user●
Create the interface endpoint●
Accept the connection request●
Configure the connection and test it●
Keep the load balancer target current after a database failover●

The exchange

StepEdmundCustomer
1Provides its AWS account ID and region; for the Shared Cloud Deployment (SaaS) they are listed in Setup. If the database is in a different region, the connection is cross-Region and Setup lists the extra requirementsBuilds the endpoint service, then sends the service name and the database details
2Creates the interface endpoint, which sends a connection requestAccepts the connection request
3Tests the connection: login, schema, test query—

Security summary

ConcernHow it is addressed
Public internetNot used; traffic stays inside AWS
Who can connectOnly Edmund’s AWS account, after the customer accepts the connection
What Edmund can reachOnly the port behind the customer’s load balancer
Access to Edmund’s systemsNone; connections are opened only from Edmund’s side
Revoking accessThe customer rejects the endpoint connection; see Setup

Terms

TermMeaning
Endpoint serviceThe customer’s database port, published through PrivateLink
Service nameThe identifier of the endpoint service, com.amazonaws.vpce.<region>.vpce-svc-…. Edmund needs it to connect
Allowed principalAn AWS account permitted to request a connection. Only Edmund’s account is listed
Interface endpointEdmund’s side of the connection, inside Edmund’s network
Network Load BalancerThe customer’s internal load balancer that forwards the connection to the database