The only limitation in this case is the region. The solution can only be deployed in Northern Virgina (us-east-1). As figure 5 shows this solution contains two EC2 instances, one for the SAP frontend (this contains a pre-installed and pre-configured SAP GUI) and a high performance r4 instance for the SAP backend (SAP Application Server on SAP HANA Database).
The following components will be installed on the virtual machines:
- SAP Kernel 7.49 Linux on x86_64 64bit
- SAP HANA Platf. Ed. 1.0 (SAP HANA DB 1.00.122.07)
- NetWeaver AS ABAP 7.51 Innovation Package SP02
More details about the landscape in the official Getting Started document.
Create your SAP landscape with a simple click
After it has been decided that the SAP solution fits to our needs, start the deployment by clicking on the Create Instance button in the right upper corner. SAP shows the terms and conditions before the deployment starts. As usual you can accept it by clicking on the I accept button. Furthermore we have to choose an existing AWS account (which has been registered before) . SAP CAL as well asks about the name of the stack, region (only us-east-1 for SAP NetWeaver AS ABAP 7.51 SP02 on HANA, Developer Edition) and a password. The password will be used for:
- Master user of the database server (user: system)
- HANA adminstrator (user: hdbadm)
- ABAP administrator (user: a4hadm)
- SAP System Administrator (user: sapadm)
- Initial password for Administrator user on the SAP Frontend instance.
After clicking on Create, the stack with a Windows 2012 R2 Server instance for SAP Frontend and a SUSE Linux Enterprise Server 12 SP 3 instance for SAP Backend will be created. That’s all, if we choose basic mode. Creation can can take up to 30 minutes.
For sure, it is possible to optimize the stack using advanced mode, like deploying to an existing Virtual Private Cloud (VPC) and subnet within AWS. It is also possible to select different EC2 instance types and change the storage sizes of the Elastic Block Storage (EBS) volumes. SAP as well gives you the opportunity to change the inbound rules of the security groups used by the instances.
Congratulations – SAP Landscape is up and running
After a successful deployment, the status changes to Active. This means, your SAP landscape is ready to be used.