Preinstalled SAP ERP 6.0 EHP8 Linux/MaxDB (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 email@example.com
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.
|MaxDB Software Owner||sdb|
|ASCS Instance Number||01|
|PAS Instance number||10|
|SAP Software Owner||lnkadm|
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 MaxDB 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.
Log on to Amazon Market Place: https://aws.amazon.com/marketplace/pp/B077GTDMQM and click on Continue to Subscribe
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): (http://service.sap.com/instguides) (http://service.sap.com/quicksizer) (http://service.sap.com/sap/support/notes/1656099)
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.
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.
Add Tags. Next step is to tag the instance so you can identify it in the AWS Console.
Configure Security Group. You should adapt these settings to meet your specific security policies. More information in Part 2 - Important SAP and HANA ports
Review Instance Launch. Review the configuration and click on Launch when accepted.
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.
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.
SAP External Ports: https://wiki.scn.sap.com/wiki/display/TCPIP/Application+Server+ABAP
Part 3 – SSH connection to your SAP AWS instance #
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 Actionsmenu, and click on
Startin the pull down menu.
Make a note of the IP address assigned to the instance. You will need it to connect to this SAP instance in AWS.
SSH to the instance with
ec2-userand 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>
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: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html 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 MaxDB Studio to MaxDB Database access #
To manage the MaxDB database, you need to install the Hana studio program on a PC/laptop, you can download it from the SAP website (https://launchpad.support.sap.com) with S-User credentials. To connect you have to enter the connection data of the instance created in AWS.
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 (https://launchpad.support.sap.com) with S-User credentials. To connect you have to enter the connection data of the instance created in AWS.
Part 5 – Configure SAP #
- Get the instance’s hardware key to obtain the license from the SAP Service Marketplace issuing the following command as the lnkadm user (it should be the same as the hardware key obtained in the HANA Licensing step)
- Go to https://support.sap.com/keys-systems-installations/keys.html and obtain a valid license key for your system (SID LNK and the hardware key obtained in the preceding step). Now you have a text file with the license.
- Start the SAP instace by executing the following commands connected to a shell as
- Configure SAPGUI to access the SAP Server. Change the IP for the one obtained during instance launch.
- Logon to SAP with SAPGUI to Client 000, with user SAP* and Password
- To install the SAP license, go to transaction
SLICENSE, click on
New Licensesif needed, click
Installand insert the text file you received from SAP.
- 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 ERP EHP8 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 SAP #
Start the SAP instace by executing the following commands connected to a shell as
Stop SAP ERP EHP8 on AWS instance #
Stop SAP #
Stop the SAP instace by executing the following commands connected to a shell as