SAP BW/4HANA 2.0 Suse (SAP License not included)

In this section you will find the required information to start using your SAP BW/4HANA 2.0 Suse instance in just minutes.


What does the instance include

EC2 instance comes with the following products:

  • SAP Netweaver 7.50 ABAP
  • SAP HANA 2.0 SP04 database
  • SuSE Enterprise Server 15.1

EC2 & SAP information

The following table shows the relevant information about the SAP software installation included in the AMI.

SAP ASCS Instance Number01
SAP PAS Instance Number10
SAP Administrator Userlnkadm
SAP HANA Instance Number00
SAP HANA Administrator Userlnhadm
Master PasswordZaq12wsXXX

Password Change

It is mandatory to change the Database installation Master Password so that it remains private to you and meets all security requirements.

Deploy your instance

Follow the next steps to deploy your new SAP instance:

  1. Log on to Amazon MarketPlace in new window

  2. Search for "Preinstalled SAP BW/4HANA 2.0 Suse" and access the product

  3. Click on Continue to Subscribe.

  4. Choose an Instance Type Select one of the AWS instance size from the available choices.

  5. Configure Instance Details Configure and define a network and subnet. If you need to connect directly by internet you need to enable Auto-assign Public IP.

  6. Add Storage. You can choose the EBS volume type, you can leave as default or use SSD / IOPS for best performance. In this point you can increase the size of the volumes to expand the filesystems. It depends on the size of the database you are going to use.

  7. Add Tags. Next step is to tag the instance so you can identify it in the AWS Console.

  8. Configure Security Group. You have to open the necessary ports in AWS security Group to allow the connection.

    This is the list of most important ports for SSH, SAP and HANA: alt text

    SAP HANA External Ports

    Find additional information in in new windowalt text

  9. Review Instance Launch. Review the configuration and click on Launch when accepted.

  10. The process will ask you to provide an existing Key Pair or to create a new one. If you choose to create a new one, do not forget to download the Key Pair file as this will be mandatory to access the EC2 instance through SSH.

  11. After a few minutes, you can access your instance with SSH and do the final configuration steps.

Post-Deployment Steps

For some actions you will need to access your EC2 instance via SSH. To do so, follow the next steps:

License your SAP HANA database

SAP HANA 2.0 SP05 Suse database comes without a valid SAP License on it, so the first time that you try to access it you will get a message similar to this:

Access to Tenant (SAP) DB

To activate SAP HANA database you must provide the system with a valid license. Follow the next steps to activate the server:

  1. Connect to the SYSTEMDB database by using SAP HANA Studio or command line tools. The following examples will be based on SAP HANA Studio.

  2. The first time you connect to Hana studio an error message will appear to inform that you need a proper license. License Error

  3. Click on the Checking license properties... link in the warning message, or access the Properties of the server in the drop down menu. Access to Tenant (SAP) DB

  4. Note down the Hardware Key for the license request in SAP Portal.

  5. Go to in new window and obtain a valid license for your deployed SAP HANA database following the SAP License Keys for the SAP HANA Database Guide in new window

  6. Download the license to your computer.

  7. Go back to Properties section in SAP HANA Studio.

  8. Click on Install a license

  9. Choose your downloaded license file and Accept

  10. If no error is displayed means that your SAP HANA database has been correctly licensed

EBS Pre-warming

We recommend you run some pre-warming commands the first time you start the system to increase performance from the beginning. First time you launch an instance from an AMI, the process synchronizes the snapshots that compose this AMI with the EBS volumes of your instance. This can take a long time depending on the size of the disks and the instance type you have chosen. Depending on the instance, it can run out of storage credits and perform at its baseline (3 iops x gb), this situation becomes a bottleneck. The process can take up to 12 hours with a m4.4xlarge instance.

Follow next steps to do so:

AWS Documentation Guide

All these steps are based on the official AWS Documentation: in new window

  1. Connect via ssh to your EC2 instance by following the steps in the AWS Documentation Guide []( in new window

  2. The first time you start SAP may take longer (up to 1 hour) since the disks in AWS are still not stable. The successive starts will be immediate.

EBS pre-warming

This is the AWS document that explains these steps: in new window It will only be necessary to perform these actions once after the creation of the Instance In our case the commands to be executed are as follows, please note, it can take up to 12 hours for all these commands to execute successfully depending on EBS size and types chosen for your instance. If you do not execute these actions, the first time you run HANA it will take a long time to boot.

  1. Now you are ready to start working with your HANA instance!!

Maintenance operations

Start SAP

SAP HANA database should start automatically when you start your EC2 instance, but in case it fails it can be started manually by following next steps:

  1. Connect via SSH to your EC2 instance as describe in the previous section.

  2. From the ec2-user shell, jump into the lnhadm user:

    sudo su - lnhadm
  3. Then start the SAP HANA database by executing:

    HDB start
  4. Once started, jump back to the ec2-user shell:

  5. Back into the ec2-user shell, jump now into the lnkadm shell:

    sudo su - lnkadm
  6. Start the SAP BW/4HANA instance by executing the following commands:

sapcontrol -nr 01 -function Start
sapcontrol -nr 10 -function Start


To stop the SAP HANA database, execute the following command connected to a shell with user lnhadm:

  1. Connect via SSH to your EC2 instance as describe in the previous section.

  2. From the ec2-user shell, jump into the lnkadm user:

    sudo su - lnkadm
  3. Stop the SAP BW4HANA instances:

    sapcontrol -nr 10 -function Stop
    sapcontrol -nr 01 -function Stop
  4. Jump back to the ec2-user shell.

  5. From the ec2-user shell, jump into the lnhadm user:

    sudo su - lnhadm
  6. Then stop SAP HANA database by executing:

HDB stop