Prerequisites and Deployment Readiness

Objective

After completing this lesson, you will be able to identify the technical and organizational prerequisites for a production Edge Integration Cell deployment and outline the ELM-based deployment process.

Introduction

Lessons 2.1–2.5 have explained what EIC is, how it works architecturally, how communication between cloud and private runtime is managed, and how it appears to integration developers and administrators in the SAP Integration Suite Cockpit. Before you can start working with EIC in practice, a set of technical and organizational prerequisites must be in place. This lesson provides the planning overview.

This lesson is intentionally a planning overview, not an installation guide. Detailed step-by-step deployment procedures are covered in the SAP Help Portal documentation for Edge Lifecycle Management and in SAP's administration courses. The goal here is to ensure that when deployment begins, the necessary foundations are already in place - and that the right teams have been engaged in advance.

The Prerequisite Areas

Before an EIC instance can be deployed and placed into service, six categories of prerequisites must be addressed:

Prerequisite AreaCore Question
SAP Licensing and SAP Business AI Platform EntitlementsDoes the organization have the right SAP Integration Suite license and the correct service plan and roles activated?
Kubernetes EnvironmentIs a supported Kubernetes cluster available, appropriately sized, and operationally ready?
External Service DependenciesAre the required database and caching services provisioned and accessible?
Network and ConnectivityCan the EIC runtime communicate outbound to SAP Business AI Platform endpoints? Can source systems reach EIC endpoints?
Edge Lifecycle Management SetupIs ELM accessible to the deployment administrator, and has cluster registration been prepared?
User Roles and AccessHave the necessary roles been assigned to the people who will perform activation and deployment?

How this lesson is organized

The six prerequisite areas above represent the complete checklist. In this lesson, they are grouped into three sections by responsibility:

  • SAP-Side Prerequisites - covers Areas 1 and 6: licensing, entitlements, and the roles needed to perform activation and deployment. These are resolved in the SAP BTP cockpit by the tenant administrator.

  • Infrastructure Prerequisites - covers Areas 2, 3, and 4: the Kubernetes cluster, external database and cache services, and network connectivity. These are resolved by the customer's infrastructure and network teams.

  • Deployment Process - covers Area 5: Edge Lifecycle Management setup and the step-by-step deployment sequence, including available hyperscaler accelerators. This is where the preceding prerequisites come together into action.

Every item from the six areas is addressed - the grouping simply follows who is responsible for what.

SAP-Side Prerequisites

License Requirements

Edge Integration Cell is available as part of SAP Integration Suite under the following license types:

  • Standard Edition
  • Enhanced Edition (SAP's current higher-tier offering - includes AI capabilities, Advanced Event Mesh, and one Edge Integration Cell tenant)
  • CPEA (Cloud Platform Enterprise Agreement)
  • PAYG (Pay as You Go)

Important: EIC is NOT available with the Starter Edition of SAP Integration Suite. Organizations on Starter Edition must upgrade to one of the above license types before activating EIC.

SAP BTP Subaccount Setup

The following SAP BTP entitlements must be active in the relevant subaccount:

  • SAP Integration Suite subscription (Standard, Enhanced, CPEA, or PAYG)
  • edge_integration_cell service plan - this entitlement enables the Runtime tab in SAP Integration Suite Settings
  • Edge Lifecycle Management service entitlement

One Edge Node is included in every qualifying SAP Integration Suite subscription (Standard, Enhanced, CPEA, PAYG - not available with Starter Edition). Additional EIC instances beyond the base allocation require a separate add-on entitlement. Organizations planning multiple EIC deployments - one per region or one per production site - should clarify the licensing implications early in the project.

Required Roles

Administrators and operators working with EIC need the following roles in SAP BTP:

Role CollectionPurposeTypical User
Integration_ProvisionerRequired to activate and configure SAP Integration Suite, including EIC activation in Settings → RuntimeIntegration Suite Administrator
EdgeLMAccessRequired for users who need access to the Edge Lifecycle Management (ELM) interfaceEdge Node Administrator
PI_Integration_DeveloperRequired to design, deploy, and monitor Integration Flows and select the target runtime at deployment timeIntegration Developer

These are SAP BTP Role Collection names. The corresponding BTP role collections are assigned via the SAP BTP cockpit (Security → Users → Role Collections).

Note

The 6-step deployment process later in this lesson references four organizational roles (Project Team, Infrastructure Team, Integration Suite Administrator, Edge Node Administrator). The table above maps the SAP BTP role assignments needed by the SAP-facing roles. The Infrastructure Team and Project Team do not require SAP BTP roles - their work is on the Kubernetes and organizational level.

Infrastructure Prerequisites

Kubernetes Environment

  • Microsoft Azure AKS
  • Amazon EKS
  • Google GKE
  • SUSE Rancher / RKE2
  • Red Hat OpenShift

Note

Always verify the currently supported Kubernetes versions for each platform in the SAP Help Portal. The supported version ranges change with each EIC release.

In addition to the supported platform, the Kubernetes cluster must meet the following infrastructure requirements:

  • Load Balancer: A load balancer integrated with the Kubernetes infrastructure is required to expose EIC endpoints and distribute traffic across Worker Pods. On cloud-managed Kubernetes platforms (AKS, EKS, GKE), this is provisioned automatically via a Kubernetes LoadBalancer Service. On on-premise clusters (SUSE Rancher, OpenShift), a virtual IP or external load balancer must be configured manually. If client IP filtering is required for API policies, a Network Load Balancer (NLB) that preserves the client IP address must be used.
  • Persistent Storage (RWO and RWX): The cluster must support automatic dynamic provisioning of PersistentVolumes in two access modes: ReadWriteOnce (RWO) for single-node storage (stateful EIC components, runtime data) and ReadWriteMany (RWX) for shared file-system storage (e.g., SNC library, optional Java heap dumps). This is provided via a StorageClass with a compatible CSI driver. Unit 3 explains the Kubernetes PersistentVolume model in detail.
  • Container Image Architecture - linux/amd64 only: EIC container images are built exclusively for linux/amd64. ARM-based worker nodes (e.g., AWS Graviton, Azure Ampere) are not supported. Infrastructure teams must ensure that all worker nodes provisioned for EIC use x86-64 (amd64) processors.

For production deployments, two external services must be provisioned by your infrastructure team: a relational database (PostgreSQL or SAP HANA) and an in-memory data store (Redis, Valkey or SAP HANA). Both require TLS. Planning implication: provisioning these services takes time - initiate early in the project timeline.

Cluster sizing depends on message volume and iFlow complexity. Use SAP Note 3705131 (EIC Sizing Guidelines) to determine the required resources before provisioning.

Note

Unit 3 explains the Kubernetes concepts behind all of the above requirements (PersistentVolumes, LoadBalancer Services, Namespaces, and ELM-managed deployment) and provides the detailed technical specifications.

External Service Dependencies

For production EIC deployments, SAP requires external, managed instances of the following services. Cluster-internal instances are suitable only for test/development environments.

PostgreSQL or SAP HANA (relational database)

EIC uses a relational database for persistent storage of integration artifacts, message store data, and Message Processing Logs. PostgreSQL is the primary and default option; SAP HANA was added as an alternative in Q1 2026. For production, this must be an externally managed instance - for example, Azure Database for PostgreSQL, Amazon RDS for PostgreSQL, or a self-managed enterprise PostgreSQL or SAP HANA installation. TLS must be enabled.

Redis, Valkey or SAP HANA (in-memory data store)

EIC uses an in-memory data store for caching within the runtime. Three options are available:

  • Redis - the primary and recommended option. Supported versions: 6.x and 7.x.
  • Valkey - added as an open-source Redis-compatible alternative in Q1 2026. Supported versions: 8.0–8.2.
  • SAP HANA - added in Q1 2026 as an alternative that can serve as both the relational database and the in-memory data store, replacing both PostgreSQL and Redis/Valkey in a single service.

For production, the data store must be an externally managed instance - for example, Azure Cache for Redis or Amazon ElastiCache for Redis. TLS must be enabled for all options.

Why external services are required for production: Cluster-internal database and caching instances introduce failure coupling between the EIC application and the infrastructure layer - if the Kubernetes cluster experiences issues, the data persistence layer is affected too. External services provide the operational reliability and data durability appropriate for production integration workloads.

Planning implication: Provisioning external database and caching services takes time - especially in organizations with formal change management processes for database provisioning. This should be initiated early in the project timeline, in parallel with other preparation work.

Network Requirements

Outbound HTTPS connectivity required

The EIC runtime must be able to reach SAP Business AI Platform cloud endpoints. All communication is outbound from the Kubernetes cluster - initiated from the private side. No inbound ports need to be opened from the internet to the Kubernetes cluster for EIC's operational communication.

Required outbound access: HTTPS (port 443) from the Kubernetes cluster nodes to SAP Business AI Platform endpoints.

Corporate proxy support

If outbound internet traffic is routed through a corporate proxy server, the proxy settings must be configured during EIC bootstrapping. EIC supports proxy configuration for outbound communication.

DNS resolution

The Kubernetes cluster must be able to resolve the DNS names of SAP Business AI Platform cloud endpoints. This requires that the cluster's internal DNS configuration correctly forwards external queries to a DNS resolver with internet access.

Inbound access for integration traffic (internal)

While EIC's operational communication with SAP Business AI Platform is outbound-only, the EIC runtime must receive integration messages from source systems within the private network. Source systems (for example, SAP S/4HANA) must have network access to the EIC runtime's integration endpoints within the private network. For pure ground-to-ground scenarios, this configuration remains entirely internal.

Network Resilience Planning

EIC can continue processing messages for up to 4 hours without an active connection to SAP Integration Suite (see Lesson 2.4). During this period, locally cached security material is used, and already-deployed Integration Flows continue to process messages normally. However, the following operations require an active cloud connection:

  • New deployments or updates to Integration Flows
  • Credential rotation and security material refresh
  • Access to Message Processing Logs via the cloud Cockpit
  • Software updates via the Repository-Based Shipment Channel (RBSC)

Planning implication: Network teams should ensure that the outbound HTTPS connection to SAP Business AI Platform is monitored and has appropriate redundancy. Define a Recovery Time Objective (RTO) for cloud connectivity loss that is well within the 4-hour window.

Security Considerations

EIC's communication model is designed with security in mind: all connections to SAP Business AI Platform are outbound-initiated (no inbound firewall ports required), TLS-encrypted, and mediated through the Cloud Connector. Database and cache connections must also use TLS encryption. For production deployments, apply your organization's standard Kubernetes security policies (RBAC, audit logging, network segmentation) and credential management practices. Detailed security hardening is beyond the scope of this introductory course.

Sizing

Resource requirements for the EIC Kubernetes cluster depend on message volume and iFlow complexity. SAP provides a dedicated sizing tool to support this planning:

General sizing guidance (indicative minimum baseline values):

ConfigurationIndicative CPUIndicative RAMIndicative Storage
Non-HA (Test/Dev)~10 cores~32 GiB~101 GiB
High Availability (Production)~20 cores~64 GiB~204 GiB

These are minimum baseline values for total cluster resource requirements (sum of all EIC component requests). Additional capacity is needed for Kubernetes control plane overhead, OS processes, monitoring/logging components, and growth in message volume. For workload-specific sizing, always validate using the tool in SAP Note 3705131 before provisioning

Note

Sizing should be validated before cluster provisioning, not after. Resizing an operational cluster is possible on managed Kubernetes services but introduces operational risk during production workloads.

Deployment Process

Hyperscaler Accelerators

To simplify the complex infrastructure setup for hyperscaler deployments, deployment accelerators are available for the two most common platforms:

Azure AKS Accelerator (by Microsoft)

Microsoft provides a Terraform-based Infrastructure-as-Code accelerator for deploying EIC on Azure Kubernetes Service. It automates the provisioning of the AKS cluster, Azure Database for PostgreSQL, Azure Cache for Redis, Azure Container Registry, and the network configuration for SAP Business AI Platform connectivity. The accelerator offers both a Quick Start (pilot/PoC) path and a Production-Ready (High Availability) path.

AWS EKS (by SAP)

SAP provides reference architectures and sample scripts for deploying EIC on Amazon Elastic Kubernetes Service, covering Amazon EKS cluster setup, Amazon RDS for PostgreSQL, Amazon ElastiCache for Redis, and connectivity to SAP Business AI Platform.

Note

The AWS materials include reference architectures on SAP Architecture Center and community resources. These are reference guides rather than a fully automated Terraform-based accelerator equivalent to the Azure accelerator. Verify the current state of available tooling at the SAP Architecture Center.

Planning implication: These resources can simplify infrastructure provisioning but assume that the prerequisites described in this lesson are already in place

The ELM Deployment Process: 6 Steps

Once all prerequisites are in place, the EIC deployment follows this six-step high-level process managed through Edge Lifecycle Management:

StepActionWho
1Verify prerequisites - Confirm licensing, SAP Business AI Platform entitlements, roles, and network connectivity are in placeProject team
2Size the cluster - Validate that the cluster has sufficient resources based on SAP sizing guidelines (SAP Note 3705131)Infrastructure team
3Activate EIC in SAP Integration Suite Settings - Complete the EIC activation step in Settings → Runtime to obtain the ELM URL and establish the SAP Business AI Platform-to-ELM trust relationshipIntegration Suite Administrator
4Validate the Kubernetes cluster - ELM performs automated validation checks against the registered cluster: Kubernetes version, available resources, network reachabilityEdge Node Administrator
5Register the Edge Node - The administrator registers the Kubernetes cluster with ELM as an Edge Node, establishing the cluster's identity within the ELM platformEdge Node Administrator
6Deploy the EIC Solution - ELM deploys the EIC software components to the registered Edge Node. This is the actual installation step.Edge Node Administrator

Important: The 6-step process involves sequential dependencies. Cluster provisioning, database setup, and network configuration must all be complete before ELM validation (Step 4) can begin. Plan these workstreams in parallel to avoid sequential project delays.

Note

ELM's built-in validation: During Step 4, ELM performs automated prerequisite checks - including connectivity to SAP Business AI Platform endpoints, Kubernetes API server access, storage class availability, and load balancer provisioning. This automated validation is valuable but it is not a substitute for thorough pre-deployment planning. Some prerequisites (external database provisioning, network firewall rules, role assignments) cannot be verified by ELM automatically and must be confirmed manually before the deployment process begins.

Post-Deployment Validation

After deploying EIC via ELM, validate the installation with the following checks:

  • ELM Health Dashboard: All EIC components show status "Running" (green).
  • SAP Integration Suite Cockpit: The EIC runtime appears in Settings → Runtime with status "Active".
  • Recommended practice: Deploy a simple test Integration Flow to the EIC runtime and confirm it appears in the Monitor with status "Completed". This end-to-end smoke test confirms that artifact deployment, message routing, and monitoring all function correctly on the new EIC instance. (This is a recommended operational practice; it is not a prescribed SAP step in the official deployment procedure.)

For detailed monitoring and troubleshooting procedures, see Unit 4.

50% Billing for EIC Messages

Messages processed by an EIC instance are billed at 50% of the standard SAP Integration Suite message rate. SAP positions this reduced rate as a cost incentive for deploying integration workloads on customer-managed infrastructure. Organizations should factor this into their total cost of ownership analysis alongside the infrastructure and operational costs of running an EIC instance.

Scenario Check-In: Global Manufacturing AG

Global Manufacturing AG has completed their readiness assessment. The SAP Business AI Platform tenant is on Enhanced Edition and the edge_integration_cell service plan is available. The Frankfurt plant already operates a Kubernetes cluster (SUSE Rancher/RKE2) for container workloads - it will be assessed against EIC sizing requirements using SAP Note 3705131. The infrastructure team has confirmed that the cluster can provision PersistentVolumes in both RWO and RWX access modes, and a load balancer is available for exposing EIC endpoints within the Frankfurt network.

Two action items require additional coordination: the DBA team must provision the external PostgreSQL and Redis instances required for production EIC use, and the network security team must create and validate the outbound HTTPS rules for SAP Business AI Platform endpoints. The SAP Business AI Platform tenant administrator has been identified and will be assigned the Integration_Provisioner and EdgeLMAccess role collections before the ELM registration step begins. With these actions tracked and in progress, the project team considers the planning phase substantially complete.

Key Takeaways

In this lesson, you identified the technical and organizational prerequisites for deploying Edge Integration Cell in a production environment. You learned that EIC requires a valid SAP Integration Suite license (Standard, Enhanced, CPEA, or PAYG - not Starter Edition), specific SAP BTP entitlements (edge_integration_cell service plan, Edge Lifecycle Management), and appropriate role collections (Integration_Provisioner, EdgeLMAccess, PI_Integration_Developer).

On the infrastructure side, you identified that EIC requires: a supported Kubernetes platform (AKS, EKS, GKE, Rancher/RKE2, or OpenShift) with linux/amd64 worker nodes; a load balancer for exposing EIC endpoints; persistent storage supporting both RWO and RWX access modes; externally managed database (PostgreSQL or SAP HANA) and in-memory data store (Redis, Valkey, or SAP HANA - both with TLS); and outbound HTTPS (port 443) connectivity to SAP Business AI Platform.

You also outlined the ELM-based deployment process: verify prerequisites, size the cluster (SAP Note 3705131), activate EIC in Settings → Runtime, validate and register the Kubernetes cluster in ELM, and deploy the EIC solution. EIC messages are billed at 50% of the standard SAP Integration Suite message rate.

Further Resources

SAP Discovery Center - Integration Suite Service Plans

https://discovery-center.cloud.sap/serviceCatalog/integration-suite?region=all&tab=service_plan

SAP Help Portal - Setting Up and Managing Edge Integration Cell

https://help.sap.com/docs/integration-suite/sap-integration-suite/setting-up-and-managing-edge-integration-cell

SAP Help Portal - Personas for Cloud Integration (Role Collections)

https://help.sap.com/docs/integration-suite/sap-integration-suite/persona-2937e5ca6ef448cfb21451a2461cc2a6

SAP Help Portal - Plan Your Setup of Edge Integration Cell

https://help.sap.com/docs/integration-suite/sap-integration-suite/plan-your-setup-of-edge-integration-cell

SAP What's New

https://community.sap.com/t5/integration-blog-posts/q1-2026-product-highlights-sap-integration-suite/ba-p/14376750

SAP Help Portal - Hybrid Deployment Using Edge Integration Cell

https://help.sap.com/docs/integration-suite/sap-integration-suite/hybrid-deployment-using-edge-integration-cell

SAP Help Portal - Network and Communication Security for EIC

https://help.sap.com/docs/integration-suite/sap-integration-suite/network-and-communication-security-for-edge-integration-cell

SAP Help Portal - ELM Prerequisite Validation Procedures

https://help.sap.com/docs/edge-lifecycle-management/documentation/prerequisite-validation-procedures

SAP Help Portal - Operating Edge Integration Cell

https://help.sap.com/docs/integration-suite/sap-integration-suite/operating-edge-integration-cell

SAP Community FAQ - Frequently Asked Questions on Edge Integration Cell

https://community.sap.com/t5/integration-blog-posts/frequently-asked-questions-faq-on-edge-integration-cell/ba-p/13571636

SAP Learning - Accelerating Hybrid Integrations with SAP Integration Suite on SUSE Rancher

https://learning.sap.com/courses/accelerating-hybrid-integrations-with-sap-integration-suite-on-suse-rancher?searchId=77ef47a2-830b-47f9-94de-48e01f9cdbf9&listPosition=1

SAP Learning - Accelerating Hybrid Integrations with SAP Integration Suite on RedHat OpenShift

https://learning.sap.com/courses/accelerating-hybrid-integrations-with-sap-integration-suite-on-redhat-openshift?searchId=844069e5-6d89-4cb1-8fb9-abc1d6c982f6&listPosition=1

SAP Learning - Accelerating Hybrid Integrations with SAP Integration Suite on Microsoft Azure

https://learning.sap.com/courses/accelerating-hybrid-integrations-with-sap-integration-suite-on-microsoft-azure?searchId=ef0f0b45-41ed-4b80-994d-ea9e679b9676&listPosition=1

SAP Architecture Center - EIC on Hyperscalers

https://architecture.learning.sap.com/docs/ref-arch/0a229d

SAP Learning - Setting Up Edge Integration Cell

https://learning.sap.com/courses/accelerating-hybrid-integrations-with-sap-integration-suite-on-microsoft-azure/setting-up-edge-integration-cell_a5fb6496-7ee4-4e45-9457-6ca70fc30f72