SAP Private Link Service
A private network connection between a selected SAP BTP service and a selected service in an application's own account with a partner cloud provider, so the traffic between them never touches the public internet.
SAP Private Link service establishes a private connection between selected SAP BTP services and selected services in an account with a partner IaaS provider, reusing the private-link functionality those providers already offer. It lets an application reach a private service endpoint instead of that service's public one, avoiding public endpoints when the two accounts connect across the account boundary, and it moves the resulting traffic over the private network instead of the public internet. It covers only the services SAP lists as selected on each side, running on SAP BTP, Cloud Foundry environment.
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 1
- Regions
- 30
- Support component
- BC-CP-PRIVATELINK
Connections
Reaching remote systems without addresses or credentials in the code
@sap/approuter patterns in front of SAP Private Link Service
Spring Boot apps routing AWS SDK traffic over SAP Private Link
Cloud Foundry runtime of SAP BTP for polyglot applications
Download
What’s New
from SAP Help Portal, readNew Regions Available
New Region Available
New Region Available
New Region Available
New Region Available
SAP Private Link Service on Google Cloud Platform in SAP BTP
New Region Available
New Region Available
New Region Available
Additional Amazon Web Services available on SAP BTP Cloud Foundry regions
Deletion of the SAP Private Link service managed Private DNS zones attached to the SAP BTP Cloud Foundry regions.
Additional Azure service available on SAP BTP Cloud Foundry regions
Additional Amazon Web Services available on SAP BTP Cloud Foundry regions
Additional Azure services available on SAP BTP Cloud Foundry regions
General Availability
Additional Azure services available on SAP BTP Cloud Foundry regions
Additional Amazon Web Services available on SAP BTP Cloud Foundry regions
Additional Azure services available on SAP BTP Cloud Foundry regions
Additional Azure services available on SAP BTP Cloud Foundry regions
Additional Azure services available on SAP BTP Cloud Foundry regions
Additional Amazon Web Services available on SAP BTP Cloud Foundry regions
Additional Azure services available on SAP BTP Cloud Foundry regions
Additional Amazon Web Services available on SAP BTP Cloud Foundry regions
SAP Private Link Service on Amazon Web Services in SAP BTP
Additional Azure services available on SAP BTP Cloud Foundry regions
Additional Azure services available on SAP BTP Cloud Foundry regions
Additional Azure services available on SAP BTP Cloud Foundry regions
General Availability
Support for Additional Cloud Foundry Regions
Others providing
Compare all 15 on the Destinations page →- SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btpNamed, credentialed addresses of other systems resolved at runtimefrom BTP/BAIP
- com.sap.cds:cds-feature-remote-odatacom.sap.cds:cds-feature-remote-odataA CAP Java feature for consuming remote OData V2 and V4 services as Remote Services, translating CQN queries into OData requests against a destination or a service binding.sap official, capRemote Services for consuming OData V2 and V4 APIs in CAP Javafrom CAP
- com.sap.cds:cds-integration-cloud-sdkcom.sap.cds:cds-integration-cloud-sdkA CAP Java feature that integrates the SAP Cloud SDK, so features such as remote OData and enterprise messaging resolve a destination or service binding and reach a remote REST-based service.sap official, capSAP Cloud SDK integration for remote REST services in CAP Javafrom CAP
- capire/s4capire/s4A pre-built integration package for SAP S/4HANA, holding the imported service definitions a CAP project would otherwise generate for itself.sap official, capPrebuilt SAP S/4HANA integration package for CAP projectsfrom CAP
- cdsecdseResolves a destination from a CAP project's own configuration, then makes the outbound call with axios: the url, the method and the body are written at the call site.independent, capDestination resolution and axios calls from CAP configurationfrom CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtimefrom CAP
- @sap-cloud-sdk/connectivity@sap-cloud-sdk/connectivityDestination lookup and the connectivity proxy — the package that turns a destination name into a reachable endpoint with credentials attached.sap official, capDestination lookup and connectivity proxy for the Cloud SDKfrom CAP
- @sap-cloud-sdk/http-client@sap-cloud-sdk/http-clientThe HTTP client that carries a destination's credentials, so an outbound call inherits the authentication rather than assembling it.sap official, capHTTP client carrying a destination's credentialsfrom CAP
- @sap-cloud-sdk/odata-common@sap-cloud-sdk/odata-commonThe shared machinery under the SDK's OData and OpenAPI client generators; a dependency of the generated clients rather than something written against directly.sap official, capShared machinery under the Cloud SDK's OData and OpenAPI clientsfrom CAP
- @sap-cloud-sdk/openapi@sap-cloud-sdk/openapiGenerated OpenAPI clients for the Cloud SDK, so a REST API described by a specification is called through typed functions.sap official, capGenerated OpenAPI clients for the Cloud SDKfrom CAP
- @sap-cloud-sdk/resilience@sap-cloud-sdk/resilienceTimeouts, retries and circuit breaking around a remote call, so one slow downstream system does not take the application with it.sap official, capTimeouts, retries and circuit breaking around remote callsfrom CAP
- @sap-cloud-sdk/util@sap-cloud-sdk/utilGeneral utilities shared across the Cloud SDK packages — a dependency, not a thing to reach for on its own.sap official, capGeneral utilities shared across the Cloud SDK packagesfrom CAP
- btp-cloud-connector-setup-automationbtp-cloud-connector-setup-automationA Yeoman generator that adds the Cloud Connector system mappings for an XS Advanced system and writes the matching SAP BTP destination files.sap official, btpYeoman generator for Cloud Connector mappings and BTP destinationsfrom BTP/BAIP
- @sapmentors/cds-scp-api@sapmentors/cds-scp-apiA Node module for CAP that calls an external API through a destination instead of a hardcoded endpoint, taking its address, credentials and on-premise tunnel from the SAP Destination and Connectivity services.community org, capNode module for CAP calling external APIs through a destinationfrom CAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- SAP's Discovery Center lists the runtime as a required service of the plan, and npm run check:catalogue listed the relation with no edge. Basis entitlement: the catalogue says a plan cannot be bought without it, which is commercial and is not drawn as a runtime dependency (vocab PERSPECTIVES, 2026-09-22).
- First seen.
For your agent
- Ref
artifact:btp-private-link-service- JSON
- /artifacts/btp-private-link-service.json
- MCP
- Connecting an agent