Private Link + CAP + PostgreSQL on AWS

[Willem_Pardaens]

Hi.

I have a private link set up pointing to a PostgreSQL database running on AWS. The private link service itself is already provisioned and configured on the BTP side. What I need to understand is how to wire this up properly in a CAP Node.js project.

Does @cap-js/postgres automatically route queries through the private link once the service is bound to the app, or does it need additional configuration to know it should use that network path?

I also added the private link service as a requires entry in the SRV module inside mta.yaml, so the binding is there at runtime. But I am not sure if that alone is enough for CAP to pick up the database connection through it, since there is no standard PostgreSQL service instance, just the private link binding exposing the endpoint.

Is binding it in mta.yaml the right approach, or is there something else needed on the CAP or adapter level to make this work end to end?

server.js

mta

Requires SRV with private link 

package.json

#privatelink #btp #capnodejs #cap #postgres #postgresoncap

[Willem_Pardaens]

I have never tried it like that, but it should work in my opinion. If you want an explicit entry to postgres in the mta, just add it as an existing service. Postgres is not an officially supported end-service for Private Link (see https://help.sap.com/docs/private-link/private-link1/supported-services-for-amazon-web-services-in-s...) but you could always point it to a generic VPC endpoint and route from there based on the port.

[fabi2295]

@Willem_Pardaens 

Thank you for the response, I'll test it and I'll come back with the answer if it works.