SAP S/4 HANA 1710 Suse

Preinstalled SAP S/4 HANA Release 1710 Suse (SAP License not included) #

Our team of consultants is continuously working on updating available AMIs and adding new products. In case you miss something, please let us know by sending an e-mail to

SAP Installation data #

During the SAP software installation in this AMI some options had to be chosen to complete the installation. Chosen options are detailed below.

  • SAP Instances: This AMI includes a database instance, an ABAP SAP Central Services (ASCS) and Primary Application Server (PAS) or Central Instance (CI).

The following table shows the relevant information about the SAP software installation included in the AMI. Information such as SAP SID, Master Password, Instance number and software location in the server are shown here.

SAP Instance Values
Hostname s4h1709suse
Domain linkeit.local
Master Password Zaq12wsX
HANA Instance Number 02
HANA Admin User s4hadm
ASCS Instance Number 01
PAS Instance number 00
SAP Software Owner s4dadm

PASSWORD CHANGE: It is mandatory to change the SAP and Database installation Master Password so that it remains private to you and meets all security requirements.
Important: SAP GUI and HANA Studio are not installed in the AMI. You will need to install SAP GUI software in order to be able to connect and login into your SAP Instance, and HANA Studio to administrate HANA Database.

Getting Started #

Part 1 - Create your own SAP instance on AWS #

Start your new SAP server by following the next steps.

  1. Log on to Amazon Market Place: and click on Continue to Subscribe

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

    For HANA database, a minimum of 61Gb memory is required (SAP HANA on AWS). For more detailed information about SAP Business Suite Sizing and appropriate EC2 instance types, please refer to SAP documentation, SAP sizing tool and OSS Notes (S-User required): ( ( (

  3. 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.

  4. 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.

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

  6. Configure Security Group. You should adapt these settings to meet your specific security policies. More information in Part 2 - Important SAP and HANA ports

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

  8. 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.

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

Part 2 - Important SAP and HANA ports #

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:

To open other specific ports this is the list of the most important. alt text

SAP External Ports: alt text
Hana External Ports: alt text

Part 3 – SSH connection to your SAP AWS instance #

  1. In the EC2 console, navigate to instances. This will list all your instances in Amazon EC2. Make sure the SAP instance you want to connect to is in “running” state. If not, choose the instance, then click on Instance Actions menu, and click on Start in the pull down menu.

  2. Make a note of the IP address assigned to the instance. You will need it to connect to this SAP instance in AWS.

  3. SSH to the instance with ec2-user and the key pair chosen at launch time. To access your instance: 1.Open an SSH client. (Recommended - find out how to connect using PuTTY) 2.Locate your private key file (.pem). 3.Connect to your instance using its IP:


        ssh -i "<keypair_location>/<keypair>.pem" ec2-user@<IP Addr>


  4. 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.

    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. This is the AWS document that explains these steps: 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 SAP it will take a long time to boot.

Part 4 – Configure HANA Studio to HANA Database access #

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

Connect to the database #

To manage the HANA database, you need to install the Hana studio program on a PC/laptop, you can download it from the SAP website ( with S-User credentials. To connect you have to enter the connection data of the instance created in AWS.

Access to SystemDB Access to Tenant DB
Access to System DB Access to Tenant (SAP) DB

We need to configure SAP Hana Studio to install the new license. The first time you connect to Hana studio an error message will appear to inform that you need a proper license. License Error To install it see the next part.

Licensing SAP HANA #

To install the HANA license, you should be to connected to Hana studio. If you are still not connected, follow the steps in the previous section to connect and ensure that database is started.

When you try to connect to HANA Database first time in Hana Studio, you get the error: Access to Tenant (SAP) DB

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

You can also obtain the hardware key by executing the following command from shell with the s4hadm user:

saplicense -get

Once you have the Hardware Key you must request for a new license key in SAP Portal. Go to and obtain a valid license key for your HANA system.

You can find additional information on how to create a license in the following link:

Part 5 – Configure SAP #

  1. Get the instance’s hardware key to obtain the license from the SAP Service Marketplace issuing the following command as the s4dadm user (it should be the same as the hardware key obtained in the HANA Licensing step)
saplicense -get
  1. Go to and obtain a valid license key for your system (SID s4d and the hardware key obtained in the preceding step). Now you have a text file with the license.
  2. Start the SAP instace by executing the following commands connected to a shell as s4dadm:
sapcontrol -nr 01 -function Start
sapcontrol -nr 00 -function Start
  1. Configure SAPGUI to access the SAP Server. Change the IP for the one obtained during instance launch.

Access to Tenant (SAP) DB

  1. Logon to SAP with SAPGUI to Client 000, with user SAP* and Password Zaq12wsX (Case Sensitive).
  2. To install the SAP license, go to transaction SLICENSE, click on New Licenses if needed, click Install and insert the text file you received from SAP.
  3. A succesfull message should be received.

Ready to work #

Now you are ready to start working with your SAP instance!!

PASSWORD CHANGE: Remember that it is mandatory to change the SAP and Database installation Master Password so that it remains private to you and meets all security requirements.

Additional Information #

Start/Stop processes #

Start SAP S/4HANA 1710 on AWS instance #

In order to be able to connect to your Instance for starting SAP software you need to connect by ssh software as explained in previous Part.

Start HANA #

HANA instance should start automatically, but in case it fails it can be started connected to a shell with user s4hadm:

HDB start
Start SAP #

Start the SAP instace by executing the following commands connected to a shell as s4dadm:

sapcontrol -nr 01 -function Start
sapcontrol -nr 00 -function Start

Check that the instance is running by executing the following the command ps -fu s4hadm. The output should be similar to this:

s4h1709suse:~ # ps -fu s4hadm
UID         PID   PPID  C STIME TTY          TIME CMD
s4hadm     4965      1  0 Jun03 ?        00:00:00 /usr/lib/systemd/systemd --user
s4hadm     4969   4965  0 Jun03 ?        00:00:00 (sd-pam)
s4hadm     5033      1  0 Jun03 ?        00:00:01 /usr/sap/S4H/HDB02/exe/sapstartsrv pf=/usr/sap/S4H/SYS/profile/S4H_HDB02_vs4h1709suse -D -u s4hadm
s4hadm    70565      1  0 Jun03 ?        00:00:00 sapstart pf=/usr/sap/S4H/SYS/profile/S4H_HDB02_vs4h1709suse
s4hadm    70574  70565  0 Jun03 ?        00:00:01 /usr/sap/S4H/HDB02/vs4h1709suse/trace/hdb.sapS4H_HDB02 -d -nw -f /usr/sap/S4H/HDB02/vs4h1709suse/daemon.ini pf
s4hadm    70591  70574  4 Jun03 ?        00:24:17 hdbnameserver
s4hadm    70932  70574  1 Jun03 ?        00:07:57 hdbcompileserver
s4hadm    70934  70574  1 Jun03 ?        00:08:18 hdbpreprocessor
s4hadm    70972  70574 52 Jun03 ?        04:16:56 hdbindexserver -port 30203
s4hadm    70974  70574  1 Jun03 ?        00:09:36 hdbxsengine -port 30207
s4hadm    71584  70574  1 Jun03 ?        00:07:59 hdbwebdispatcher

Stop SAP S/4HANA 1710 on AWS instance #

STop SAP #

Stop the SAP instace by executing the following commands connected to a shell as s4dadm:

sapcontrol -nr 10 -function Stop
sapcontrol -nr 01 -function Stop
Stop HANA #

To stop the HANA server, execute the following command connected to a shell with user s4hadm:

HDB stop