Terraform Modules for SAP are a subcomponent designed to be used from the Terraform Templates for SAP, but can be executed individually.

These custom Terraform Modules for SAP enable different solution scenarios of SAP software installations, and are used where there is siginificant repeated code, such as bootstraping a new Cloud Account with a new Resource Group, VPC and Subnets - i.e. a 'Minimal Landing Zone'.

Every Terraform Template (e.g. /sap_hana_single_node_install/aws_ec2_instance):

• will reference Terraform Modules for SAP infrastructure platforms (e.g. /aws_ec2_instance/host_provision)
• will reference Terraform Modules for SAP solution scenarios (e.g. /all/ansible_sap_s4hana_install_maintplan)

It is possible to create your own Terraform Templates and re-use other Terraform Modules from the Terraform Registry, although these combinations are not tested; for example:

• Terraform Module for the Cloud Service Provider's defined landing zone patterns (e.g. Azure Cloud Adoption Framework (CAF))
• Terraform Module for SAP Host provision to a specified Infrastructure Platform (e.g. /msazure_vm/host_provision subdirectory)
• any of the Terraform Modules for SAP installations using Ansible (e.g. /all/ansible_sap_s4hana_install_maintplan subdirectory)

For more information which explains Terraform Modules, please see:

• Terraform HCL Language - Syntax of Module Blocks
• Terraform HCL Language - Creating Modules

Each Cloud and Hypervisor are not designed the same, each will have different interpretations and implementation of computing concepts.

Additionally, the implementations change over time - whether this is "Previous Generation" environments from a Cloud Service Provider, or a "Major.Minor" version update from a Hypervisor vendor.

Therefore it is not possible to match precisely the same functionality when bootstrapping and installing SAP software. For this reason the bootstrap of an environment is kept separate from existing resources.

In addition, dependant upon the additional configuration and policies within an existing configured environment - these Terraform Modules for SAP may not work at all and may require custom changes to fit the bespoke environment.

For further information, please see below for the Infrastructure provisioning parity comparison table.

N.B. Contributions to these Terraform Modules need to retain as much parity across each infrastructure platform.

Please note, for all SAP software installations the execution time will vary based on multiple factors:

• Infrastructure provision time
• Installation media downloads time from SAP.com
• Storage volume used for downloads and database backup files (default is lowest cost / slowest speed when using Cloud IaaS)

All detailed execution permissions are listed in the documentation for the Terraform Modules of each Infrastructure Platform. See the next section.

The below table lists the Terraform Modules for SAP, and any detailed documentation:

_Key:

• ✅ _{Ready and Tested}
• ⚠️ _{Pending work}
• ❌ _{Not available yet}
• 🚫 _{Capability not provided by vendor (or construct concept does not exist)}