The SAP Private Link service establishes a private connection between selected SAP BTP services and selected services in your own IaaS provider accounts. By reusing the Private Link functionality of SAP’s partner IaaS providers, the service lets you access your services through private network connections to avoid the need for public endpoints or data transfer via the public internet. In addition to the functionality that is already generally available for the SAP Private Link service on Azure, we’re happy to announce that we now offer Beta support for SAP Private Link service on AWS.

What does the Beta include?

With SAP Private Link service, Cloud Foundry applications running on SAP BTP with Amazon AWS as IaaS provider can communicate with services that support AWS PrivateLink via a private connection. This ensures that traffic is not routed through the public internet, but stays within the AWS network infrastructure.

For the Beta, the SAP Private Link service supports connections to custom AWS Endpoint Services as well as the following AWS Services:

The Beta will be initially available on the following SAP BTP Cloud Foundry regions:

• cf-eu10 – Europe (Frankfurt)
• cf-us10 – US East (VA)

We plan to provide support for additional SAP BTP Cloud Foundry regions running on AWS over the course of the Beta.

Connection from SAP BTP, Cloud Foundry environment to AWS using Private Link service

What are possible use cases?

One possible use case is to use the SAP Private Link service to communicate with an SAP S/4HANA system or other SAP or non-SAP systems running on a VM in your own AWS account privately from within SAP BTP, Cloud Foundry environment.

This connection can be established by creating an AWS Endpoint Service that exposes an AWS Network Load Balancer which routes traffic to the SAP S/4HANA system. The service name of that AWS Endpoint Service must then be used to create an SAP Private Link service instance. As soon as the connection is established successfully, the SAP Private Link service provides a private hostname pointing to your AWS Endpoint Service.

Connection from SAP BTP, Cloud Foundry environment to an AWS Load Balancer

The second use case is to use the service name of one of the supported services offered by AWS instead of a custom service name. The basic functionality is the same, but instead of a connection to a custom endpoint exposed via an AWS Endpoint Service, the connection will be established to a service natively provided by AWS, such as the Simple Queue Service.

Connection from SAP BTP, Cloud Foundry environment to AWS SQS using Private Link service

How can I use it?

Check out our tutorials about how to

What to expect after Beta?

Currently, we support custom AWS Endpoint Services as well as a selection of services natively provided by AWS.

In the future, we plan to support the following:

• Google Cloud as IaaS provider and the corresponding Google Cloud Private Service Connect
• Connections to other selected native AWS services, e.g. AWS Lambda
• Connections initiated from within AWS to SAP BTP, Cloud Foundry environment or other SAP BTP services
• Connections from or to other SAP BTP services, e.g. to SAP HANA Cloud

Please understand that SAP does not commit to, promise to, and is under no legal obligation to deliver these features in the future. This list of features may be changed or withdrawn by SAP at any time for any reason without notice, and business decisions shoult not be based on this.

Important Links

• Official documentation

Conclusion

Now you know that the SAP Private Link service on AWS has to offer for its initial Beta release, with support for the SAP BTP, Cloud Foundry environment on AWS and several selected AWS services.

Get started with the Beta! We’re eager to receive your feedback!