Configuration Steps for Network Load Balancer

Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/

On the navigation pane, under LOAD BALANCING, choose Target Groups.

Choose Create target group.

For Name, type an easily identified target group name for the sap-ascs instance. (For example, type sap-ascs for your ASCS overlay IP address).

For Target type, select IP.

For Protocol, choose TCP.

For Port, type 36<ASCS instance number>. For example: 3600, where 00 is the instance number.

For Health checks, keep the default health check settings, or change settings based on your requirements.

Choose Create.

Repeat steps 1 to 9 to create target group for JDBC/SQL port 3<instance number>15 and SAP HANA HTTP port 5<instance number>13 to access your SAP HANA instance with the respective overlay IP address.

Choose the Targets tab, then choose Edit.

Choose Add to register your targets.

Choose the Network drop-down and select Other private IP address. Then, enter the ASCS overlay IP address and choose Add to list.

Repeat steps 11 to 13 to register JDBC/SQL and HTTP ports with the respective overlay IP address.

On the EC2 navigation pane, under LOAD BALANCING, choose Load Balancers.

Choose Create Load Balancer.

For Network Load Balancer, choose Create.

For Name, type a name for your load balancer. For example, sap-ha-nlb.

For Scheme, choose internal. An internal load balancer routes requests to targets using private IP addresses.

For Listeners, under Protocol, choose TCP. For Port, specify the ASCS port (36< SAP Instance number>. For example, use 3600 if your SAP instance number is 00.

For Availability Zones, select the VPC and subnets where the SAP instances with HA setup are deployed.

For Tags, choose Add Tags and for Key, type Name. For Value, type the name of the network load balancer, such as sap-ha-nlb.

Choose Next: Configure Security Settings.

Ignore the warning that appears and choose Next: Configure Routing. (In this scenario, the network load balancer is used as pass through without any SSL termination. For end-to-end encryption, use SNC from SAP GUI to SAP Instance.)

For Target group, choose Existing target group and select the sap-ascs target group created earlier.

Choose Next: Register Targets.

Choose Next: Review.

Choose Create.

Repeat the steps 1 to 14 to create another Network Load Balancer for SAP HANA setup with Network Load Balancer TCP protocol listener to JDBC/SQL port 3<instance number>15. Choose VPC and the subnets where the primary and secondary SAP HANA database is deployed and register the target JDBC/SQL target group.

Add an additional listener to the Network Load Balancer created in step 14 with SAP StartSrv/HTTP port 5<instance number>13 listener port and register the target StartSrv/HTTP port target group.

Open the Amazon VPC console at https://console.aws.amazon.com/vpc/

In the navigation pane, choose Route Tables, and select the Amazon VPC routing table where your SAP instance is deployed.

Choose Actions, Edit routes.

For Destination, specify your overlay IP address. For Target, specify the SAP instance Elastic Network Interface.

Choose Save routes.

In the Load Balancers section of the EC2 console, make a note of the Network Load Balancer DNS name for the sap-ha-nlb.

Start SAP Logon.

Choose New, then Next.

In the System Entry Properties box, for Connection Type, choose Group/Server Selection.

For Message Server, type the Network Load Balancer DNS name, and choose OK.

In the Load Balancers section of the EC2 console, make a note of the Network Load Balancer DNS name for the JBDC/SQL and SAPStartSrv/HTTP ports.

In the Host Name parameter of SAP HANA Studio, use the Network Load Balancer DNS name and provide additional credentials to connect to the SAP HANA system.