Skip to Content
Product Information
Author's profile photo Philipp Becker

SAP Private Link Service for AWS (Beta) is Available

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. See also the announcement from AWS on this.

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%20from%20SAP%20BTP%2C%20Cloud%20Foundry%20environment%20to%20AWS%20using%20Private%20Link%20service

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%20from%20SAP%20BTP%2C%20Cloud%20Foundry%20environment%20to%20an%20AWS%20Load%20Balancer

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%20from%20SAP%20BTP%2C%20Cloud%20Foundry%20environment%20to%20AWS%20SQS%20using%20Private%20Link%20service

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

  1. Set Up SAP Private Link Service on Amazon Web Services (Beta)
  2. Connect SAP Private Link Service to AWS PrivateLink Service

Besides that, we also provide a collection of sample apps that demonstrate how the AWS SDK has to be configured so that the traffic goes over Private Link.

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

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!

Assigned Tags

      9 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Damian Tometzki
      Damian Tometzki

      Hello Mr. Becker,

       

      many thanks for the article.

      Is then still a HANA Cloud Connector necessary ?

       

      VG

      Damian

       

      Author's profile photo Philipp Becker
      Philipp Becker
      Blog Post Author

      Hi Damian,

      I assume that with "HANA Cloud Connector" you mean the SAP Cloud Connector? That depends on your concrete scenario. The SAP Private Link service is not a general replacement for the SCC, but can make the SCC obsolete in some scenarios. Also the scope of both solutions is slighly different. The SAP Private Link service provides L3 network connectivity with the guarantee that the data will stay within the IaaS providers network backbone, whereas the SCC has other functionality included like, e.g., RFC filtering.

      So providing a general statement on whether the SAP Cloud Connector is still necessary is not possible.

      Best regards,
      Philipp Becker

      Author's profile photo Damian Tometzki
      Damian Tometzki

      Hello Mr. becker,

       

      great many thanks

      Author's profile photo Martin Pankraz
      Martin Pankraz

      Hi Damian Tometzki,

      I maintained a comparison here.

      KR

      Martin

      Author's profile photo Damian Tometzki
      Damian Tometzki

      great many thanks

      Author's profile photo Gopal Vangala
      Gopal Vangala

      Long wait is finally over. When can we expect this in mainstream support?

      Author's profile photo Philipp Becker
      Philipp Becker
      Blog Post Author

      Hi.

      If by "mainstream support" you mean on whether the SAP Private Link service on AWS will leave the beta and become ready for production: We're currently planning to have this in H1/2023. As with all such dates, please be aware that at the moment we cannot rule out that this date might change again without further notice, but we're working hard on making this possible.

      Best regards,
      Philipp

      Author's profile photo Abdul Musavir
      Abdul Musavir

      Can we use the "Sap Private network service" to connect the IoT service that is hosted on AWS  with Kafka service that is hosted on SAP Cloud foundry ? if not , are these services planned in future.

      Author's profile photo Philipp Becker
      Philipp Becker
      Blog Post Author

      Hi,

      At the moment we unfortunately do not yet have plans to support connections to Kafka hosted on SAP BTP CloudFoundry, although that might change in the future.

      Best regards,
      Philipp