Deployment Ownership Models

The ownership model refers to the location of the region where the Mission Control Agent and software event brokers are installed. These are the variants of ownership:

  • Public Regions: Dedicated event broker services are deployed in SAP-controlled shared VPC/VNets on public cloud providers such as Amazon Web Services (AWS), Google Cloud Platform (GCP), and Azure.
  • Dedicated Regions: Dedicated event broker services are deployed in SAP-controlled VPC/VNets dedicated to the customer on public cloud providers such as AWS, GCP, and Azure.
  • Customer-Controlled Regions (sometimes referred to as Customer Private Regions): Dedicated event broker services are deployed in a customer's on-premises or cloud-based Kubernetes cluster, such as OpenShift, Rancher (RKE1), Amazon (EKS), Azure (AKS, ARO), Google (GKE), Alibaba (ACK), Huawei (CCE), and more.

For a list of supported deployment locations, see Deployment Regions.

For the complete list of supported Kubernetes environments, see Deployment Architecture for Kubernetes.

If you require a deployment to a region in China, these deployments are supported only for Customer-Controlled Regions. Deployments at this time are not supported in Public Regions or Dedicated Regions. For more information, see Deployments in China.

Public Regions

For the simplest deployment, event broker services are deployed within the customer's account in advanced event mesh for SAP Integration Suite, using the customer's choice of cloud provider and region. In this scenario, the software event brokers are dedicated to the customer and not shared. Because SAP maintains control over this deployment, there isn't any additional customer overhead when adding services or regions. This is the standard deployment option, and is described in Getting Started with SAP Integration Suite, Advanced Event Mesh.

Illustration depicting the concepts described in the surrounding text.

Use Cases

This ownership model is a good choice when:

  • Applications and clients can connect over public internet
  • There are cost-sensitive workloads
  • The fastest time to market is required
  • A development or proof-of-concept environment is needed

Dedicated Regions

In this deployment configuration, event broker services are deployed in a region owned by SAP and dedicated to the customer. In this dedicated virtual network, SAP deploys a Mission Control Agent to orchestrate event broker services. The agent creates a secure connection back to the Home Cloud and relays user commands from the console to the software event brokers. SAP maintains control of the address space and network security groups.

Illustration depicting the concepts described in the surrounding text.

With advanced event mesh deployed in a Dedicated Region, SAP installs all the components with the sizing required by the customer. In this scenario, SAP maintains the infrastructure, but the customer may provide the VPC/VNet and subnet CIDR blocks. Depending on the connectivity model, the customer may be required to provide sufficient information to establish network peering between the SAP and customer virtual networks.

Use Cases

This model is a good choice if:

  • Single-tenant VPC/VNet ( i.e., network traffic isolation) is important
  • Connectivity to on-premises applications and network is required
  • The customer prefers VPC/VNet management and security concerns to be included in the SaaS offering

Customer-Controlled Regions

For this scenario, event broker services are installed in a customer's on-premises or cloud-based Kubernetes cluster. Advanced event mesh uses Kubernetes StatefulSets to manage the deployment of event broker services.

Illustration depicting the concepts described in the surrounding text.

Use Cases

This type of deployment is a good choice for:

  • Hybrid (cloud and on-premises) event mesh use cases
  • Data movement between legacy and Kubernetes-based applications
  • Highly sensitive data that cannot be on the cloud
  • Situations where an on-premises deployment is a requirement for other reasons (e.g., all applications are on premises)

Supported Platforms

Deployment of the Customer-Controlled Region follows a process that begins after you've met with SAP and defined requirements with them.Your deployment will be easier if you supply certain information to the SAP team. The questions listed in the Questionnaire: Deploying in a Customer-Controlled Region section guide you through the things you should consider before you deploy advanced event mesh.

For details about the architecture of advanced event mesh in a Kubernetes cluster and a summary of the details to deploy advanced event mesh, see Deployment Architecture for Kubernetes.