One Connect Deployment - AWS PreRequisites

One Connect Deployment - AWS PreRequisites

Technical Prerequisites for Proof of Concept (PoC)

Kubernetes Deployment Options

The OneConnect Platform can be deployed on Minikube or vanilla Kubernetes clusters. However, for better scalability and operational simplicity, we recommend using Amazon EKS with Fargate, especially when running on AWS.

Note: Running on EKS with Fargate simplifies resource management and is more production-aligned for PoC evaluations.

Minimum Resource Requirements

Kubernetes Environment

  • CPU & Memory:
    • Mid-tier node recommended
    • RAM: Minimum 12 GB (16 GB preferred for higher stability)
  • Storage:
    • Persistent Volume (PVC): 50 GB
    • Ephemeral Disk Space: 100 GB

Database Requirements

  • Memory: At least 20 GB RAM
  • CPU: Mid-range (4–8 vCPUs, depending on query load and concurrency)
Note: These specifications are intended for PoC purposes. For production use, additional scaling and optimization may be required based on actual workloads.

Pre-installation Requirements for OneConnect Platform on AWS EKS

To successfully deploy the OneConnect Platform on an Amazon EKS cluster, ensure the following prerequisites are met in the environment where installation will be performed:

1. AWS CLI v2 Installed and Configured

  • The AWS Command Line Interface (CLI) version 2 must be installed.
  • Authenticate the AWS CLI using programmatic credentials (access key and secret key).
  • The credentials must have access to the AWS region where the EKS cluster is provisioned.

Validation Command:

aws sts get-caller-identity

2. kubectl Installed

  • kubectl must be installed on the same machine where AWS CLI is configured.
  • The installed version should be compatible with the Kubernetes version running in your EKS cluster.

3. Amazon EKS Cluster Provisioned

  • Ensure that an existing Amazon EKS cluster is already deployed in the target AWS region.

4. Required IAM Permissions

  • The AWS CLI-authenticated user must have the following AWS managed IAM policies attached:
    • AmazonEKSAdminPolicy
    • AmazonEKSClusterAdminPolicy

5. Configure kubectl for EKS Access

Configure your kubectl to connect to the EKS cluster with the following command:

aws eks update-kubeconfig --region <REGION> --name <CLUSTER_NAME>

Verify successful configuration:

kubectl get pods

Expected Output:

No resources found in default namespace.

6. Verify kubeconfig apiVersion

  • Open the kubeconfig file at ~/.kube/config.
  • Ensure the apiVersion under the exec section is set to:
apiVersion: client.authentication.k8s.io/v1beta1
This helps prevent compatibility issues in certain environments.

7. Network CIDR Blocks

  • Provide the following CIDR blocks for network configuration and validation:
    • The CIDR block of the VPC where the EKS cluster is deployed.
    • The CIDRs of the subnets used by the EKS worker nodes (especially relevant for Fargate deployments).

8. Docker Hub Access

  • Ensure the installation environment can reach and authenticate with Docker Hub.
  • This is required to pull OneConnect Platform container images.

Validation Command:

docker login

    • Related Articles

    • One Connect Cloud Deployment

      Prerequisites Download the required .zip folders attached at the end of the document: sql.zip one-connect.zip kafka-compose.zip Requirements for the Virtual Machine System: Linux Architecture: 64-bit processors (x86_64) support Instance ...

    • OneConnect Deployment and Configuration

      One Connect Platform: Kubernetes Azure Deployment Manual for Private Network This manual outlines the steps required to deploy the One Connect system on a Kubernetes cluster within a Private Network (meaning the OneConnect Platform will not be ...

    • Establishment of the Database and Requirements

      One Connect Manual in Azure Establishment of the Database and Requirements Prerequisites For the SQL database, the following are recommended: MariaDB MySQL Download the following sql.zip file - Database Deployment Deployment Steps 1. Extract the SQL ...

    • OneConnect General Architecture

      The following representation shows a general architecture diagram for OneConnect, considering SAP ECC or S4HANA as the producer and destinations such as Clickhouse, Snowflake, and Databricks as subscribers. The OneConnect structure consists of 3 main ...

    • Onibex Clickhouse Sink Connector

      The Onibex Clickhouse JDBC connector sends real-time data from Kafka to write to Tables based on the topics subscription. It is possible to achieve idempotent writes with upserts. Auto-creation of tables and auto-evolution is supported using the ...