Deploy various SAP Software solution scenarios onto different Hyperscaler Cloud Service Providers and Hypervisors platforms.
These Terraform Templates for SAP are designed to be:
Please read the full documentation for how-to guidance, requirements, and all other details. Summary documentation is below:
SAP Software solution scenario | Infrastructure Platform |
---|---|
SAP HANA 2.0 (any version) single-node installation |
|
SAP S/4HANA (2021, 2022) single-node installation |
|
SAP S/4HANA (2020, 2021, 2022) single-node installation, using SAP Maintenance Planner Stack XML (to run SUM and SPAM / SAINT) |
|
SAP S/4HANA (2020, 2021, 2022) Distributed installation (HDB, NWAS ASCS, NWAS PAS, NWAS AAS), using SAP Maintenance Planner Stack XML (to run SUM and SPAM / SAINT) |
|
SAP S/4HANA (1909, 2020, 2021, 2022) single-node System Copy installation(Homogeneous with SAP HANA Backup / Recovery) |
|
SAP BW/4HANA (2021) single-node installation |
|
SAP ECC on SAP HANA (EHP7, EHP8) single-node installation |
|
SAP ECC on SAP HANA (EHP7, EHP8) single-node System Copy installation(Homogeneous with SAP HANA Backup / Recovery) |
|
SAP ECC on IBM Db2 (EHP7, EHP8) single-node installation |
|
SAP ECC on Oracle DB (EHP7, EHP8) single-node installation |
|
SAP ECC on SAP ASE (EHP7, EHP8) single-node installation |
|
SAP ECC on SAP MaxDB (EHP7, EHP8) single-node installation |
|
SAP NetWeaver AS (ABAP) with SAP HANA (7.50, 7.52) single-node installation |
|
SAP NetWeaver AS (ABAP) with IBM Db2 (7.50, 7.52) single-node installation |
|
SAP NetWeaver AS (ABAP) with Oracle DB (7.50, 7.52) single-node installation |
|
SAP NetWeaver AS (ABAP) with SAP ASE (7.50, 7.52) single-node installation |
|
SAP NetWeaver AS (ABAP) with SAP MaxDB (7.50, 7.52) single-node installation |
|
SAP NetWeaver AS (JAVA ) with IBM Db2 (7.50)single-node installation |
|
SAP NetWeaver AS (JAVA ) with SAP ASE (7.50)single-node installation |
|
SAP Solution Manager 7.2 SP2 (ABAP/JAVA )with SAP ASE single-node installation |
|
SAP Solution Manager 7.2 SP2 (ABAP/JAVA )with SAP HANA single-node installation |
|
Key:
The following is an overview of the Infrastructure-as-Code (IaC) provisioning, for full details please see the underlying Terraform Modules for SAP documentation.
Infrastructure Platform | Amazon Web Services (AWS) | Google Cloud | Microsoft Azure | IBM Cloud | IBM Cloud | IBM PowerVC | VMware vSphere |
---|---|---|---|---|---|---|---|
Product | EC2 Virtual Server | VM | VM | Virtual Server | IBM Power Virtual Server | LPAR | VM |
Account Init |
|||||||
Create Resource Group. Or re-use existing Resource Group | :no_entry_sign: | :no_entry_sign: | :white_check_mark: | :white_check_mark: | :white_check_mark: | N/A | N/A |
Create Networks (VPC/VNet), Subnets, and Internet Access. Or re-use existing VPC/VNet | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | N/A | N/A |
Account Bootstrap (aka. minimal landing zone) |
|||||||
Create Private DNS, Network Security | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | N/A | N/A |
Create Network Interconnectivity hub | :white_check_mark: | :no_entry_sign: | :no_entry_sign: | :white_check_mark: | :white_check_mark: | N/A | N/A |
Create TLS key pair for SSH and Import to Cloud Platform | :white_check_mark: | :no_entry_sign: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
Bastion Injection |
|||||||
Create Subnet and Network Security for Bastion | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | N/A | N/A |
Create Bastion host and Public IP address | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | N/A | N/A |
Host Network Access for SAP |
|||||||
Append Network Security rules for SAP | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | N/A | N/A |
Host NFS |
|||||||
Create NFS Share | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :warning: | N/A | N/A |
Host Provision |
|||||||
Create DNS Records (i.e. A, CNAME, PTR) | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | N/A | N/A |
Create Storage Volumes (Profile or Custom IOPS) | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :warning: no custom IOPS |
:white_check_mark: | :white_check_mark: |
Create Host/s | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
Key:
These are common SAP solution scenarios which are codified using Infrastructure Automation for SAP (Terraform) and Build Automation for SAP (Ansible). These can be extended as needed for bespoke requirements.
This does not intend (and can not) replicate every SAP software deployment scenario, and does not replace any existing SAP installation procedures detailed in the SAP Help Portal or SAP Notes on SAP ONE Support. However, with the Ansible Role for SAP SWPM it is possible to install any SAP Software which is supported by SAP Software Provisioning Manager (SWPM 1.0/2.0).
For move-fast activities, such as rapid provisioning and administration testing tasks (latest software releases and revision/patch levels, system copy restore to Cloud etc.), these Terraform Templates for SAP can be amended to suit these requirements.
For greater support in automating the lifecycle of SAP Systems themselves, it is recommended to consider SAP Landscape Management Enterprise Edition.
For greater demo and evaluation of SAP Software business functionality, it is recommended to consider SAP Cloud Appliance Library.