SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Starting point

btp-edge-integration-cell-on-azure

Step-by-step instructions for deploying SAP Integration Suite's Edge Integration Cell, a hybrid integration runtime, onto Microsoft Azure.

Edge Integration Cell manages APIs and runs integration scenarios inside a customer's own private landscape, and this repository covers the Azure side of standing one up: an Azure Virtual Network across at least two availability zones and a Kubernetes cluster on Azure Kubernetes Service at Kubernetes 1.29 to 1.33, plus a PostgreSQL 15 database, a Redis 6.x or 7.x data store and a load balancer, each of the last three marked optional and required for high availability. There are two guides, a quick setup and a high availability setup, and the minimum sizing rises from 10 CPU and 32 GiB with 101 GiB of persistent volumes to 20 CPU and 64 GiB with 204 GiB. On the SAP side it asks for a global account and subaccount and an SAP Integration Suite entitlement and subscription.

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
Demonstrates
Integration flowsBTPIntegration flowscapabilityMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is [destinations](capability:destinations), and brokering events between systems is [Event Mesh](capability:event-mesh).
Requires
SAP Integration SuiteSAP Integration Suiteartifactthe entitlement and subscription Edge Integration Cell is a runtime of; the cell is activated from the suite
Optional
PostgreSQLPostgreSQLoutside the atlasthe database an Edge Integration Cell uses at version 15, with password authentication and at least 1 CPU and 2 GiBRedisRedisoutside the atlasthe data store an Edge Integration Cell uses at 6.x or 7.x, with access key authentication and at least 1 CPU and 1 GiB

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222
@SAP-samples
maintainerAdarsh HegdePersonContributes to this
In the atlas: contributes to 2
@adarshnarayanhegde
1 contributor

What it declares

Every artifact

Type
Sample
Origin
By SAP

As a sample

Form
does not say

Connections6

btp-edge-integration-cell-on-azure connectionsbtp-edge-integration-cell-on-azurePROVIDES→ demonstrates1demonstrates authoredIntegration flowsNEEDS→ available via2available via derived Through: PostgreSQLPostgreSQL on SAP BTP, hyperscaleroptionavailable via derived Through: RedisRedis on SAP BTP, hyperscaler option→ needs1needs stated the entitlement and subscription Edge Integration Cell is a runtime of; the cell is activated from the suite SAP-samples/btp-edge-integration-cell-on-azure — README, Requirements: https://github.com/SAP-samples/btp-edge-integration-cell-on-azure SAP-samples/btp-edge-integration-cell-on-azure — README, Description: https://github.com/SAP-samples/btp-edge-integration-cell-on-azureSAP Integration Suite→ optionally needs2optionally needs stated If: a high availability setup; the requirement is marked Optional; Required for HA the database an Edge Integration Cell uses at version 15, with password authentication and at least 1 CPU and 2 GiB SAP-samples/btp-edge-integration-cell-on-azure — README, Requirements: https://github.com/SAP-samples/btp-edge-integration-cell-on-azure SAP-samples/btp-edge-integration-cell-on-azure — README, Requirements: https://github.com/SAP-samples/btp-edge-integration-cell-on-azurePostgreSQLifoptionally needs stated If: a high availability setup; the requirement is marked Optional; Required for HA the data store an Edge Integration Cell uses at 6.x or 7.x, with access key authentication and at least 1 CPU and 1 GiB SAP-samples/btp-edge-integration-cell-on-azure — README, Requirements: https://github.com/SAP-samples/btp-edge-integration-cell-on-azure SAP-samples/btp-edge-integration-cell-on-azure — README, Requirements: https://github.com/SAP-samples/btp-edge-integration-cell-on-azureRedisif

README

quoted from SAP-samples/btp-edge-integration-cell-on-azure under Apache-2.0, read
SAP-samples/btp-edge-integration-cell-on-azure/README.mdOn GitHub

Deploy SAP Integration Suite - Edge Integration Cell on Microsoft Azure

REUSE status

Description

SAP Edge Integration Cell is a hybrid integration runtime offered as part of SAP Integration Suite, which enables you to manage APIs and run integration scenarios within your private landscape.

This repository provides comprehensive instructions for deploying SAP Edge Integration Cell on Microsoft Azure. By following the guidelines provided, you can configure the necessary Azure resources and deploy SAP Edge Integration Cell.

EIC Architecture HA

For more information on Edge Integration Cell, refer to SAP Help page.

Requirements

Following infrastructure are required to deploy Edge Integration Cell on Azure.

  • SAP Prerequisites

    • SAP BTP Global Account & Subaccount.
    • SAP Integration Suite (Standard Edition or Premium Edition) Service Entitlement & Subscription.
    • (Optional) SAP Integration Suite - Edge Integration Cell service plan entitlement.
  • External Prerequisites

    • (Required) Azure Virtual Network (VNet)

      • At least 2 Availability Zones are needed for a quick start, or 3 Availability Zones with both public and private subnets for high availability.
    • (Required) Kubernetes cluster on Azure Kubernetes Service (AKS)

      • Kubernetes 1.29 - 1.33 are currently supported by Edge Integration Cell on AKS.

      • Minimum sizing per setup:

        CPU / MemoryPersistent Volumes
        non-HA10 CPU / 32 GiB101 GiB
        HA20 CPU / 64 GiB204 GiB
      • Agent / worker nodes with less than 4 CPUs should be avoided as the overhead gets quite high and pod scheduling gets more difficult.

      • A kubeconfig with cluster admin privileges is required for initializing the edge node, enabling CRUD operations on namespaces and CRDs.

      • Maximum number of pods per node depends on the chosen networking plugin and is configurable. Should be >= 50 when only a single node shall be used.

    • (Optional; Required for HA) A PostgreSQL database on Azure Database for PostgreSQL

      • PostgreSQL 15 is currently supported by Edge Integration Cell.

      • PostgreSQL authentication is only supported (Microsoft Entra ID Token authentication is not supported).

      • Minimum 1 CPU, 2 GiB memory is required for the PostgreSQL database server.

    • (Optional; Required for HA) A Redis data store on Azure Cache for Redis

      • Redis 6.x and 7.x are currently supported by Edge Integration Cell.

      • Access Keys authentication is only supported (Microsoft Entra ID Token authentication is not supported).

      • Minimum 1 CPU, 1 GiB memory is required for the Redis server.

    • (Optional; Required for HA) A Load Balancer integrated with AKS cluster

      • A load balancer integrated with your Kubernetes infrastructure to expose Edge Integration Cell endpoints and load balance traffic across K8s nodes and services.

For more information, please refer to SAP Notes 3247839

Required Infrastructure Sizing Guidelines

Understand the key components of Edge Integration Cell, the factors that influence its performance, and the methods to calculate the size for the hardware resources required.

For detailed sizing guidelines, please refer to Sizing Guide for Edge Integration Cell

Deploy SAP Edge Integration Cell on Azure

Disclaimer: The networking setup, database, and datastore configuration illustrated in this repository are currently intended as a starting point for developers. Please adhere to your organization's specific guidelines on security and network configuration. More detailed guidelines and an enhanced, secure architecture are being developed and will be made available soon.

Ready to get started? Follow the steps for either a quick setup or a high availability setup below.

Quick Setup: Simplified steps to deploy EIC on Azure

High Availability Setup: Comprehensive guide for robust EIC deployment

Known Issues

No known issues.

How to obtain support

Create an issue in this repository if you find a bug or have questions about the content.

For additional support, ask a question in SAP Community.

Contributing

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

License

Copyright (c) 2026 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP-samples/btp-edge-integration-cell-on-azuretree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, integration-and-messaging
Contributors1

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-btp-edge-integration-cell-on-azure
JSON
/artifacts/sap-samples-btp-edge-integration-cell-on-azure.json
MCP
Connecting an agent