Deploy SAP Edge Integration Cell on Amazon Elastic Kubernetes Service (EKS) - Deploy Edge Integration Cell Solution
In the previous instruction, we've added the Edge Node, established the secure connection between the Edge Lifecycle Management and the Edge Node, and deployed Edge Lifecycle Management into your Amazon EKS cluster. Well done!
Now it is time for us to deploy the Edge Integration Cell solution into your Amazon EKS cluster. Upon successfully deploying the Edge Integration Cell solution, it will make your Amazon EKS cluster a real runtime location for running Integration Flow and APIs in the SAP Integration Suite.
In this instruction, we will walk you through the steps of deploying the Edge Integration Cell solution.
- Prerequisites
- Step 1. Deploy the Edge Integration Cell Solution
- Step 2. Configure keystore for Edge Integration Cell runtime
- Step 3. Configure DNS mapping for Edge Integration Cell endpoint
- Conclusion
-
You've finish previous instruction Deploy SAP Edge Integration Cell on Amazon Elastic Kubernetes Service (EKS) - Add an Edge Node, and have Edge Node available.
-
You've finish all the previous AWS instructions, and have below information handy.
- Amazon EKS Cluster
- Have EBS storage class and EFS Storage class configured.
- Have AWS Load Balancer Controller installed. (Optional for Quick Setup)
- Have Kubernetes configuration file of your EKS Cluster handy.
- Amazon RDS (Optional for Quick Setup)
- Have Amazon RDS for PostgreSQL database created.
- Have Amazon RDS for PostgreSQL database connection endpoint point handy.
- Have Amazon RDS for PostgreSQL database user name handy.
- Have Amazon RDS for PostgreSQL database user password handy.
- Have Amazon RDS for PostgreSQL database name handy.
- Have Amazon RDS for PostgreSQL database SSL/TLS certificate file handy.
- Amazon ElastiCache (Optional for Quick Setup)
- Have Amazon ElastiCache for Redis OSS data store created.
- Have Amazon ElastiCache for Redis OSS data store connection endpoint point handy.
- Have Amazon ElastiCache for Redis OSS data store user name handy.
- Have Amazon ElastiCache for Redis OSS data store user password handy.
- Have Amazon ElastiCache for Redis OSS data store SSL/TLS certificate file handy.
- Amazon Route 53
- Have purchased host name ready in the Amazon Route 53.
- Amazon EKS Cluster
-
Open the Edge Lifecycle Management user interface. Select the Edge Node where you want to deploy the solution. Scroll down to the Deployments section, then click Deploy Solution.
-
In the Solution Information step, do following then click Next Step.
-
Solution Details
- Name: Choose Edge Integration Cell.
- Version: Choose latest version
-
Solution Properties
- For Quick Setup, DO NOT check Enable Shared File System.
- For HA Setup, Check Enable Shared File System
- Shared File System Storage Class: Enter the Amazon EFS type storage class name that we created in the instruction Amazon Elastic Kubernetes Service (EKS) Cluster Storage Configuration Guide
- Default Virtual Host: Enter a custom domain name used for exposing Edge Integration Cell endpoints under the DNS provider used in the instruction Domain and SSL Setup Guide for SAP Edge Integration Cell
- You DO NOT have to create this custom domain name record in your NDS provider, it will be created automatically during the solution deployment phase.
- Default Virtual Host Key Alias: Enter the first part of your custom domain name.
-
-
In the Dependencies step, leave everything as default, then click Next Step directly.
-
In the Edge Integration Cell Services step, do the following, then click Next Step.
-
For Quick Setup, keep everything to default and click Next Step.
-
Properties
-
Check Enable Multi AZ Support.
-
Check Enable External DB.
- External DB Hostname: Enter the Amazon RDS for PostgreSQL DB cluster writer endpoint that we created in the instruction Amazon Relational Database Service (RDS) for PostgreSQL Configuration Guide.
- External DB Port: Enter 5432 or the port number you gave when create the PostgreSQL DB cluster on Amazon RDS.
- External DB Username Enter postgres
- External DB Password: Enter the password of your PostgreSQL DB user.
- External DB TLS Root Certificate: Upload the SSL/TLS certificates of your Amazon RDS for PostgreSQL DB cluster.
-
Check Enable External Redis
- External Redis Addresses: Enter the Amazon ElastiCache for Redis OSS cluster endpoint, which we created in the instruction of Amazon ElasticCache with Redis OSS Configuration Guide
- External Redis Mode: Choose cluster or choose the mode of your Redis data store.
- External Redis Username: Enter the redis user name that we create in the instruction of Amazon ElasticCache with Redis OSS Configuration Guide
- External Redis Password: Enter the redis user password that we create in the instruction of Amazon ElasticCache with Redis OSS Configuration Guide
- External Redis TLS Certificate: Upload the SSL/TLS certificate of your redis cluster.
-
-
-
In the Istio step, do the following, then click Next Step.
- Properties
- Check Client IP Preservation check box.
- Load Balancer Provider: Choose AWS.
- Properties
-
In the Review step, click Deploy button directly to trigger the Edge Integration Cell deployment.
-
The deployment of the solution starts with the deployment of the dependent solutions Istio and Edge Integration Cell Services. Once the deployment of independent solutions are complete, the deployment of Edge Integration Cell starts automatically.
-
Once all the deployment finished, you should see the screen as below.
A keystore is used to secure message exchange both at transport level and at message level. For Edge Integration Cell, since you can have more than one keystore, you can decide whether to create a new, add, remove, or delete an existing keystore.
-
Go back to the SAP Integration Suite home page. Go to Monitor -> Integrations and APIs, choose Edge Integration Cell runtime from the Runtime drop down, and then click Keystore card.
-
In the Manage Keystore screen, select All from Runtime dropdown. Then click Create button to create a new Keystore for Edge Integration Cell runtime.
-
Select the key store you just created, then choose Add -> Key Pair to upload the key pair file of your domain to the key store.
-
In the Add Key Pair pop-up screen, do following then click Add.
-
Alias: Enter the Default Virtual Host Key Alias of your Edge Integration Cell solution deployment. You could find this value in your Edge Integration Cell deployment General tab.
-
Files: Upload the key pair file we created in the previous instruction Domain and SSL Setup Guide for SAP Edge Integration Cell
-
Password: Enter the Export Password you gave when you generate the key pair file in the previous instruction Domain and SSL Setup Guide for SAP Edge Integration Cell
-
-
Execute the
kubectl
command below to obtain the external IP address of the Network Load Balancer (NLB). NLB was provisioned automatically during the Edge Integration Cell solution deployment time. Note down the returned EXTERNAL-IP value.kubectl -n istio-system get service istio-ingressgateway
-
Go to the Amazon Route 53 console, select the hosted zone of your purchased host name, then click Create record button.
-
In the Create record screen, do following, then click Create records.
- Quick create record:
- Record name: Enter the Default Virtual Host Key Alias of your Edge Integration Cell solution deployment. You could find this value in your Edge Integration Cell deployment General tab.
- Record type:
- If the EXTERNAL-IP value of your NLB is the real IP address, choose A - Route traffic to an IPv4 address and some AWS resources.
- If the EXTERNAL-IP value of your NLB is a host name, choose CNAME - Routes traffic to another domain name and to some AWS Resources
- Value: Enter the EXTERNAL-IP value of your NLB, which obtained in the previous step.
- Quick create record:
-
Let's now verify the connectivity of the Edge Integration Cell endpoint. Go back to SAP Integration Suite home page. Go to Operate, choose the Edge Integration Cell node from the drop down. Copy and paste the virtual host name of your Edge Integration Cell node in the browser.
-
In your browser a page should open with the below error message. This indicates that the SAP Edge Integration Cell deployment has been completed and finished successfully! If the page does not open, it usually indicates an issue in the setup.
Deploying the SAP Edge Integration Cell on Amazon EKS involves a series of well-defined steps that integrate various AWS services to create a robust edge infrastructure.
By following the steps outlined in this instruction, you have successfully set up the Edge Integration Cell with necessary dependencies like external databases, Redis clusters, and secure DNS configurations.
This deployment not only ensures high availability through multi-AZ support but also provides secure communication channels through keystores and TLS certificates.
With the Edge Integration Cell now operational, your enterprise is equipped to process and analyze data at the edge, reducing latency and improving the overall efficiency of your business operations. The final connectivity verification confirms that your setup is complete and ready for use, providing a solid foundation for extending SAP's capabilities to edge environments.