An Azure managed PostgreSQL database service for app development and deployment.
Azure Database for PostgreSQL Flexible Server cannot connect directly to an AWS PrivateLink endpoint or endpoint service. Although Azure Private Link and AWS PrivateLink provide similar functionality, they are separate cloud-provider technologies and are not interoperable.
The supported approach is to establish network connectivity between your AWS VPC and the Azure virtual network, for example by using:
- Site-to-Site VPN (recommended for most deployments)
Azure ExpressRoute together with AWS Direct Connect through a supported connectivity partner for enterprise/private connectivity
Once network connectivity and DNS resolution are configured, applications running in your AWS VPC can connect to the PostgreSQL Flexible Server using its private FQDN over the private network.
The recommended architecture depends on how your Flexible Server was deployed:
Private access (Virtual Network Integration): Route your AWS VPC to the Azure VNet hosting the Flexible Server through the VPN/interconnect.
Public access: You can optionally create an Azure Private Endpoint for the server and access it over the VPN/interconnect. Note that Azure Private Endpoints are supported only for servers deployed in Public access mode.
Could you please confirm:
Is your PostgreSQL Flexible Server deployed with Private access (VNet integration) or Public access?
Do you require fully private connectivity, or is public access with firewall rules acceptable?
This information will help determine the most appropriate connectivity architecture for your environment.
References:
https://learn.microsoft.com/en-us/azure/postgresql/network/concepts-networking-private
https://learn.microsoft.com/en-us/azure/postgresql/network/how-to-networking-servers-deployed-public-access-add-private-endpoint?tabs=portal-add-private-endpoint-connections
Hope this helps, Please let us know if you have any questions.