Access AWS Launch Wizard Deploy an SAP application with AWS Launch Wizard Clone deployment

Deploying an SAP application (Console)

You can deploy an SAP application using the AWS Launch Wizard console.

Topics

Access AWS Launch Wizard
Deploy an SAP application with AWS Launch Wizard
Clone deployment

Access AWS Launch Wizard

You can launch AWS Launch Wizard from the AWS Launch Wizard console located at https://console.aws.amazon.com/launchwizard.

Deploy an SAP application with AWS Launch Wizard

The following steps guide you through deploying an SAP application with AWS Launch Wizard after you have launched it from the console.

Create a deployment

From the AWS Launch Wizard landing page, choose Create deployment.
Choose SAP.
Under Permissions, Launch Wizard displays the AWS Identity and Access Management (IAM) roles required for Launch Wizard to access other AWS services on your behalf. For more information about these roles and setting up IAM for Launch Wizard, see Identity and Access Management for AWS Launch Wizard. Choose Next.

Define infrastructure

On the Define infrastructure page, define your deployment name and infrastructure settings.

Under the General subheading, define the following:
- Deployment name. Enter a unique application name for your deployment.
- Description (Optional). Provide an optional description of your deployment.
- Enable rollback on failed deployment. By default, if a deployment fails, your provisioned resources will not be rolled back/deleted. This default configuration helps you to troubleshoot errors at the resource level as you debug deployment issues. If you want your provisioned resources to be immediately deleted if a deployment fails, select the check box.
- Create an AWS Service Catalog product. Select the check box to package and export AWS CloudFormation templates and associated application configuration scripts to Amazon S3 and create an AWS Service Catalog product. You use these scripts to deploy and configure AWS infrastructure resources for SAP applications. If you select this option, the templates and scripts are saved to the specified Amazon S3 path. You can use the saved AWS CloudFormation templates and AWS Service Catalog products for repeated deployments of the SAP applications using CloudFormation, AWS Service Catalog, and third-party applications integrated with AWS Service Catalog.
- Tags (Optional). Enter a key and value to assign metadata to your deployment. For help with tagging, see Tagging Your Amazon EC2 Resources.
Under the Infrastructure – SAP landscape subheading, configure the following infrastructure settings for your SAP landscape.
Configuration options
Under Configuration type, choose whether to Create new configuration or Apply saved configuration.

Enter the following information:

Configuration name. Enter a name or short description to identify your configuration. You can save this configuration for future use.

Deployment environment. (Create new configuration, only) Choose whether to deploy into a Production or Non-Production environment.
Configuration details
If you choose to create a new configuration, enter the following information.
Key pair name. Choose an existing key pair from the dropdown list or select the link to create one. If you select Create new key pair name, you are directed to the Amazon EC2 console. From the Amazon EC2 console, under Network and Security, choose Key Pairs. Choose Create a new key pair, enter a name for the key pair, and then choose Download Key Pair.

Important
This is the only time that you can save the private key file, so download and save it in a safe place. You must specify the name of your key pair when you launch an instance, and provide the corresponding private key each time that you connect to the instance.

Return to the Launch Wizard console, and choose the refresh button next to the Key Pair name dropdown list. The new key pair appears in the dropdown list. For more information about key pairs, see Amazon EC2 Key Pairs.

Virtual Private Cloud. Choose a VPC from the dropdown list or select the Create VPC link. If you select Create VPC, you are redirected to the VPC console to create a VPC.

Availability Zone and private subnets. You can deploy into one or two Availability Zones with up to two private subnets per Availability Zone. Different requirements are needed for different systems in the landscape. You must select two Availability Zones with a required primary and optional secondary subnet for each Availability Zone. These selections are used for each deployment according to the deployment model that you selected.

From the dropdown lists, choose the Availability Zones within which you want to deploy your SAP systems and choose the private subnets. The private subnets must have outbound connectivity to the internet and to other AWS services, such as Amazon S3, AWS CloudFormation, and CloudWatch Logs. They must also be able to access the Linux repositories required for instance configuration.

For high availability deployments, the following subnets must share a common route table:

subnet 1 in Availability Zone 1 and subnet 1 in Availability Zone 2

subnet 2 in Availability Zone 1 and subnet 2 in Availability Zone 2

To create a private subnet

If a subnet doesn't have a route to an internet gateway, the subnet is known as a private subnet. Use the following procedure to create a private subnet. We recommend that you enable the outbound connectivity for each of your selected private subnets using a NAT gateway. To enable outbound connectivity from private subnets with public subnets, create a NAT Gateway in your chosen public subnet. Then, follow the steps in Updating Your Route Table for each of your private subnets.

Follow the steps in Creating a Subnet in the Amazon VPC User Guide using the existing VPC that you will use in Launch Wizard.

When you create a VPC, it includes a main route table by default. On the Route Tables page in the Amazon VPC console, you can view the main route table for a VPC by looking for Yes in the Main column. The main route table controls the routing for all subnets that are not explicitly associated with any other route table. If the main route table for your VPC has an outbound route to an internet gateway, then any subnet created using the previous step, by default, becomes a public subnet. To ensure the subnets are private, you may need to create separate route tables for your private subnets. These route tables must not contain any routes to an internet gateway. Alternatively, you can create a custom route table for your public subnet and remove the internet gateway entry from the main route table.
Verify Connectivity. Select the check box to verify that your private subnets have outbound internet connectivity.

Security groups. You can choose already existing security groups or Launch Wizard can create security groups that will be assigned to the EC2 instances that Launch Wizard deploys. If you choose already existing security groups, you must ensure that all of the necessary ports required to access the SAP and SAP HANA databases are open. If you choose to allow Launch Wizard to create the security groups, the security groups are created to enable the components of the cluster to communicate. Systems that are deployed with the same configuration settings can also communicate.

If you choose an existing security group, Launch Wizard displays the security groups that will be assigned to the EC2 instances that Launch Wizard deploys. This enables the components to communicate and systems that are deployed with the same configuration settings to communicate.

Connectivity to external systems or users. If you allowed Launch Wizard to create the security groups, then choose the Connection type and Value of the IP address or security groups required to access the SAP systems. These values can be a network segment from which the end users access the SAP systems, or downstream/upstream systems assigned a different security group in AWS or on premises.

Proxy setting. During the launch process, the deployed Amazon EC2 instances require outbound internet access in order to:

Access the operating system (SUSE/RHEL) repositories.

Access AWS services, such as Amazon S3, CloudWatch and Systems Manager.

An internet gateway is typically configured for outbound internet access. If you want to route internet traffic through a proxy server, enter the proxy server details. When proxy server information is provided, Launch Wizard will make the necessary environment changes to the EC2 instances during launch so that outbound internet traffic is routed through the proxy server.

PROXY. Enter the proxy server name and port, for example http://10.0.0.140:3128 or https://10.0.0.140.3128.

NO_PROXY. When a proxy server is used for outbound communication, the NO_PROXY environment variable is used to route traffic without using the proxy for the following types of traffic:

local communication

traffic to other instances within the VPC

traffic to other AWS services for which VPC endpoints are created

Enter a list of comma-separated values to denote hostnames, domain names, or a combination of both.

We recommend that you add all AWS service endpoints (if defined) to the NO_PROXY environment variable so that a private connection between the VPC and the service endpoint can be established in the AWS VPN. For more information on AWS service endpoints, see AWS service endpoints.

NO_PROXY is an optional parameter. If no value is entered, the following default URLs are added to the environment. Values entered for NO_PROXY at a later time are added to this list.

NO_PROXY="localhost,127.0.0.1,169.254.169.254,.internal,{VPC_CIDR_RANGE}"

Default NO_PROXY URL details

localhost—loopback hostname

127.0.0.1—loopback adapter IP

169.254.169.254—EC2 metadata link-local address

.internal—default DNS for the VPC

{VPC_CIDR_RANGE}—CIDR block of the VPC, for example, 10.0.0.0/24

Time zone. Choose the time zone settings to configure the timezone on the instances from the dropdown list.

EBS encryption. From the dropdown list, choose whether or not to enable EBS encryption for all of the EBS volumes that are created for the SAP systems. For more information, see Amazon EBS Encryption.

Domain name (DNS) settings (Optional). Select Domain Name or Route 53 from the DNS type dropdown list.

If you select Domain Name, you have the option to enter a domain name to maintain a Fully Qualified Domain Name (FQDN) in the /etc/hosts file for each instance that is launched and configured by Launch Wizard.

If you select Route 53, select a Route 53 hosted zone from the dropdown list. Launch Wizard will create a DNS entry for each EC2 instance launched.

Note
Before you use a Route 53 hosted zone, verify that the hosted zone is integrated with the VPC, and that the VPC DHCP options are correctly set up.

SAP landscape settings. Enter the system settings for your SAP landscape.

SAP System Admin User ID. Enter the user ID for the SAP system administrator.

SAP System Admin Group ID. Enter the group ID for SAPSYS. We recommend that you replicate this number across all of your SAP systems because SAPSYS GID must be the same between systems that are part of the transport domain.

SAPINST Group ID. Enter the group ID for the SAPINST.

Simple Notification Service (SNS) topic ARN (Optional). Specify an SNS topic where Launch Wizard can send notifications and alerts. For more information, see the Amazon Simple Notification Service Developer Guide. You can also choose Create SNS topic and then create one in the Amazon SNS console. After you create an SNS topic, you can enter it in the Launch Wizard SNS field.

After you specify the infrastructure settings, choose Next.

Application and deployment settings

The following steps show the deployment paths for NetWeaver stack on SAP HANA database and SAP HANA database. Please follow the deployment steps for your deployment path.

NetWeaver stack on SAP HANA database

Application settings

On the Configure application settings page, enter your NetWeaver stack on SAP HANA database application settings.

Application type. Select NetWeaver stack on SAP HANA database. This configuration includes:
- NetWeaver stack for a single instance , distributed instance, or multi-AZ for high availability (HA) deployment.
- EC2 instances for the NetWeaver application tier
- EC2 instances for SAP HANA database and optional SAP HANA database install
General settings – SAP system. Enter the settings for your SAP system.
- SAP System ID (SAPSID). An identifier for your system. The ID must be a three character, alphanumeric string.
- EBS Volume Type for NetWeaver application stack instances. Choose which volume type to use for the NW application file system /usr/sap/SAPSID from the dropdown list.
- Transport Domain Controller. Specify whether the SAP system will be the domain controller for the SAP landscape. If not, select the transport file system of the domain controller to be mounted.
- SAP Web Dispatcher. Specify whether to deploy SAP Web Dispatcher to load balance incoming web connections for your SAP application server instances.
General Settings – SAP HANA. Enter the settings for your SAP HANA installation.
- SAP HANA System ID. Enter the identifier for your SAP HANA database. The ID must be a three character, alphanumeric string.
- SAP HANA Instance number. Enter the instance number to be used for the SAP HANA installation and setup. The ID must be a two-digit number.
- EBS Volume Type for SAP HANA. Select the EBS volume types to use for SAP HANA Data, SAP HANA Logs, and SAP Others from the dropdown lists.
  
  Note
  gp3 volumes are not supported for HANA production databases running on Xen instances (X1, X1e, R4, and R3). When you deploy HANA databases with Xen instances after choosing Production as the Deployment environment under the Configuration options, gp2 volumes will be used to set up SAP HANA Data and Logs on the instances you selected for the HANA database.
- Select Make this selection to use Amazon FSx for NetApp ONTAP for all SAP HANA database file systems, except root, backup, and media file systems.
  
  Your chosen Amazon EBS volume type is used for the application layer.
After you enter your application settings, choose Next.

(Use the tab for Single instance deployment, Distributed instance deployment, or High availability deployment, depending on your configuration)

Single instance deployment

On the Configure deployment model page, enter the deployment details for a single instance deployment.

Deployment details. Launch Wizard supports single instance deployments, distributed instance deployments, and high availability deployments. Select Single instance deployment.
ASCS, PAS, and DB on one EC2 instance. Enter the deployment settings for your instance.
- Instance details.
  - Under Instance sizing, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
  - Operating System. Select a supported operating system version for the ASCS instance. For a complete list of operating system versions supported for ASCS, see Operating systems.
  - AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
  - Host name. Enter the host name for the EC2 instance.
  - Private IP address. Choose whether to use an Auto-assigned (default) IP address or a Custom IP address.
    
    Auto-assign (default). When you select this option, an IP addressed will be assigned for you. This is the default option.
    
    Private IP address. When you select this option, you can enter a single IP address. Verify that this IP address is within the subnet range of the instance you are launching.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
  - SAP Web Dispatcher ID (SID). The SID to use for SAP Web Dispatcher. This value must be unique throughout your SAP system's landscape.
  - SAP Web Dispatcher Admin User ID. The user ID number for the SAP Web Dispatcher administrator user (sid-adm).
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose instance.
  - Use AWS recommended resources.
    
    Infrastructure requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections and the EBS volumes that will be created and attached to the launched instances. This is an estimate of AWS costs to deploy additional resources and does not include any image costs, EC2 reservations, applicable taxes, or discounts.
- Under Amazon FSx for NetApp ONTAP storage, enter your desired volume sizes for SAP HANA data, log, and other file systems. The displayed default values are based on your selection of the instance type.
Pre- and post-deployment configuration scripts — optional

You can run pre- and post-deployment configuration scripts during application provisioning. For more information about how Launch Wizard accesses and deploys these scripts, see Custom deployment configuration scripts.
Pre-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Pre-deployment configuration scripts must finish running in 45 minutes or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
Post-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Post-deployment configuration scripts must finish running in 2 hours or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
After you have entered your deployment settings, choose Next.

(See the SAP software installation settings tab.)

Distributed instance deployment

On the Configure SAP HANA deployment model page, enter the deployment details for a distributed instance deployment.

Deployment details. Launch Wizard supports single instance deployments, distributed instance deployments, and high availability deployments. Select Distributed instance deployment.
ASCS/SCS Server and Primary Application Server (PAS). Enter the deployment settings for your instance.
- Instance details.
  - Under Instance sizing, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the ASCS and PAS instances. For a complete list of operating system versions supported for ASCS, see Operating systems.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
  - Host name. Enter the host name for the EC2 instances.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose your instance.
  - Use AWS recommended resources.
    
    Infrastructure requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include any applicable taxes or discounts.
Settings for Database (DB) Server. Enter the deployment settings for your instance.
- Instance details.
  - Under Instance sizing, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the ASCS and PAS instances. For a complete list of operating system versions supported for ASCS, see Operating systems.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
  - Scale up and Scale out. Select an upgrade strategy for your system hardware to upgrade for increased data and workload.
    
    Scale-up deployment.If you choose this deployment upgrade model, enter the host name for the database
    
    Scale-out deployment. If you choose this deployment upgrade model, enter the SAP HANA master host name, the Number of worker nodes, and the Worker node hostname prefix under Instance sizing.
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose instance.
  - Use AWS recommended resources.
    
    Define requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  - Instance type. Choose the instance type from the dropdown list.
  - Private IP address. Choose whether to use an Auto-assigned (default) IP address or a Custom IP address.
    
    Auto-assign (default). When you select this option, an IP addressed will be assigned for you. This is the default option.
    
    Private IP address. When you select this option, you can enter a single IP address. If you have selected multiple worker nodes, enter the IP addresses to assign to the instance for each selected node. Separate more than one IP address with commas. Verify that the IP addresses are within the subnet range of the instance you are launching. You must enter the same number of IP addresses as the number of nodes selected.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
  - Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include any applicable taxes or discounts.
- Under Amazon FSx for NetApp ONTAP storage, enter your desired volume sizes for SAP HANA data, log, and other file systems. The displayed default values are based on your selection of the instance type.
Settings for SAP Web Dispatcher. Enter the deployment settings for your SAP Web Dispatcher instance.
- Instance details.
  - Under Image type, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the SAP Web Dispatcher instances. For a complete list of operating system versions supported for SAP Web Dispatcher, see Operating systems.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
  - Private subnet. The private subnet to provision SAP Web Dispatcher instances in.
  - SAP Web Dispatcher ID (SID). The SID to use for SAP Web Dispatcher. This value must be unique throughout your SAP system's landscape.
  - SAP Web Dispatcher Admin User ID. The user ID number for the SAP Web Dispatcher administrator user (sid-adm).
  - Hostname. The hostname to use for the EC2 instance where SAP Web Dispatcher is deployed.
- Private IP address. Choose whether to use an Auto-assigned (default) IP address or a Custom IP address.
  - Auto-assign IP address (default). When you select this option, an IP addressed will be assigned for you. This is the default option.
  - Custom IP address. When you select this option, you can enter a single IP address.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
- Under Instance sizing, choose whether to Based on infrastructure requirements or Based on instance type.
  - Based on infrastructure requirements
    
    Infrastructure requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2 supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    vCPU. The amount of vCPUs cores required by the instance.
    
    Memory (GB). The amount of memory required for each instance.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
    
    SAPS. We will recommend SAP certified instance types which offer SAPS ratings for the value you enter.
    
    Based on instance type
    
    Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include any applicable taxes or discounts.
Settings for Additional App Servers (AAS) - optional. Enter the deployment settings for your AAS instances.
- Instance details.
  - Number of Additional App Servers (AAS). Enter the number of additional application servers.
  - Naming convention for host name. Enter the naming convention for the host name.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose your instance.
  - Use AWS recommended resources.
    
    Define requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include any applicable taxes or discounts.
Pre- and post-deployment configuration scripts — optional

You can run pre- and post-deployment configuration scripts during application provisioning. For more information about how Launch Wizard accesses and deploys these scripts, see Custom deployment configuration scripts.
Pre-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, choose whether to proceed with the deployment. If you do not select this option, then when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Pre-deployment configuration scripts must finish running in 45 minutes or less.
- Configuration script. You can add one or more configuration scripts depending on the number of servers you select to run scripts during the launch phase.
  - For each pre-deployment configuration script that you want to run, choose to use a script located in Amazon S3 and enter the URL path of the script, or upload a script file.
  - Select the servers to run the pre-deployment configuration scripts during the launch phase. You can choose to run pre-deployment scripts on ASCS/SCS Server and Primary Application Server (PAS), Database (DB) Server, and Additional App Servers (AAS). You can add a script for each server selected.
  - To remove a configuration script, choose Remove script. To add more configuration scripts, choose Add another script.
Post-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure, choose whether to proceed with the deployment. If you do not select this option, then when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Post-deployment configuration scripts must finish running in 2 hours or less.
- Configuration script. You can add one or more configuration scripts depending on the number of servers you select to run scripts during the post-deployment phase.
  - For each post-deployment configuration script that you want to run, choose to use a script located in Amazon S3 and enter the URL path of the script, or upload a script file.
  - Select the servers to run the post-deployment configuration scripts when an EC2 instance has been configured for use. You can choose to run the post-deployment scripts on ASCS/SCS Server and Primary Application Server (PAS), Database (DB) Server, and Additional App Servers (AAS). You can add a script for each server selected.
  - To remove a configuration script, choose Remove script. To add more configuration scripts, choose Add another script.
After you have entered your additional settings, choose Next.

(See the SAP software installation settings tab.)

High availability deployment

On the Configure SAP HANA deployment model page, enter the deployment details for the high availability deployment.

Deployment details. Launch Wizard supports single instance deployments, distributed instance deployments, and high availability deployments. Select High availability deployment.
Settings for ABAP System Central Services (ASCS) server. Enter the deployment settings for your instance.
- Instance details.
  - Under Image type, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the ASCS instances. For a complete list of operating system versions supported for ASCS, see Operating systems.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown list.
  - Host name. Enter the host name for the EC2 instance.
  - ASCS instance number. Enter the instance number for the SAP installation and setup, and to open up ports for security groups.
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose your instance.
  - Use AWS recommended resources.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2 supports up to 448 logical processors. If the amount of memory required exceeds 4 TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance type.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
- Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources. It does not include any applicable taxes or discounts.
- Under Amazon FSx for NetApp ONTAP storage, enter your desired volume sizes for SAP HANA data, log, and other file systems. The displayed default values are based on your selection of the instance type.
Settings for Enqueue Replication Server (ERS). Enter the deployment settings for your ERS.
- Instance details.
  - Under Instance sizing, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the ERS instance.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown list.
  - Host name. Enter the host name for the EC2 instance.
  - ERS instance number. Enter the instance number for the SAP installation and setup, and to open up ports for security groups.
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose your instance.
  - Use AWS recommended resources.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance type.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
- Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include any applicable taxes or discounts.
Settings for database (DB) Server. Enter the deployment settings for your database.
- Under Instance sizing, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
  - Instance details.
    
    Operating System. Select a supported operating system version for the ERS instance.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown list.
- Primary and secondary instance details. Enter details for both the primary and secondary instances.
  - SAP HANA host name. Enter the host name for the SAP HANA primary and secondary instances.
  - Server site name. Enter the primary and secondary site name for the SAP HANA system replication.
  Private IP address settings
  - Primary instance details
    
    Private IP address. Choose whether to use an Auto-assigned (default) IP address or a Custom IP address for your primary instance.
    
    Auto-assign (default). When you select this option, an IP addressed will be assigned for you. This is the default option.
    
    Private IP address. When you select this option, you can enter a single IP address. Verify that this IP address is within the subnet range of the instance you are launching.
  - Secondary instance details
    
    Private IP address. Choose whether to use an Auto-assigned (default) IP address or a Custom IP address for your secondary instance.
    
    Auto-assign (default). When you select this option, an IP addressed will be assigned for you. This is the default option.
    
    Private IP address. When you select this option, you can enter a single IP address. Verify that this IP address is within the subnet range of the instance you are launching.
- Overlay IP address. Enter the overlay IP address to assign to the active node. The IP address should be outside of the VPC CIDR and must not be used by any other HA cluster. It is configured to always point to the active SAP HANA node.
- Pacemaker tag name. Enter the tag to assign to each EC2 instance. This tag is used by the pacemaker component of SLES HAE and RHEL for SAP high availability solutions and must not be used by any other EC2 instance in your account.
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose your instance.
  - Use AWS recommended resources.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2 supports up to 448 logical processors. If the amount of memory required exceeds 4 TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance type.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
- Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources. It does not include any applicable taxes or discounts.
Primary Application Server (PAS). Enter the deployment settings for your instance.
- Instance details.
  - Under Image type, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the ERS instance.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown list.
  - Host name. Enter the host name for the EC2 instance.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable Amazon EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose your instance.
  - Use AWS recommended resources.
    
    Define requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2 supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources. It does not include any applicable taxes or discounts.
Settings for SAP Web Dispatcher. Enter the deployment settings for your SAP Web Dispatcher instances.
- Instance details.
  - Under Image type, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the SAP Web Dispatcher instances. For a complete list of operating system versions supported for SAP Web Dispatcher, see Operating systems.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
  - SAP Web Dispatcher ID (SID). The SID to use for SAP Web Dispatcher. This value must be unique throughout your SAP system's landscape.
  - SAP Web Dispatcher Admin User ID. The user ID number for the SAP Web Dispatcher administrator user (sid-adm).
- Enter the following information for both the primary and secondary instance:
  - Private subnet. The private subnet to provision SAP Web Dispatcher instances in.
  - Hostname. The hostname to use for the EC2 instance where SAP Web Dispatcher is deployed.
  - Private IP address. Choose whether to use an Auto-assigned (default) IP address or a Custom IP address.
    
    Auto-assign IP address (default). When you select this option, an IP addressed will be assigned for you. This is the default option.
    
    Custom IP address. When you select this option, you can enter a single IP address.
    
    Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
- Under Instance sizing, choose whether to Based on infrastructure requirements or Based on instance type.
  - Based on infrastructure requirements
    
    Infrastructure requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2 supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    vCPU. The amount of vCPUs cores required by the instance.
    
    Memory (GB). The amount of memory required for each instance.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
    
    SAPS. We will recommend SAP certified instance types which offer SAPS ratings for the value you enter.
    
    Based on instance type
    
    Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include any applicable taxes or discounts.
Settings for Additional App Servers (AAS) - optional. Enter the deployment settings for your AAS instances.
- Instance details
  - Number of Additional App Servers (AAS). Enter the number of additional application servers.
  - Naming convention for host name. Enter the naming convention for the host name.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable Amazon EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
- Under Instance sizing, choose whether to Use AWS recommended resources or Choose your instance.
  - Use AWS recommended resources.
    
    Infrastructure requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2 supports up to 448 logical processors. If the amount of memory required exceeds 4 TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources. It does not include any applicable taxes or discounts.
Pre- and post-deployment configuration scripts — optional

You can run pre- and post-deployment configuration scripts during application provisioning. For more information about how Launch Wizard accesses and deploys these scripts, see Custom deployment configuration scripts.
Pre-deployment configuration script — optional
- Deployment settings. Choose whether to proceed with the deployment if a configuration script fails or times out. If you do not select this option, if the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Pre-deployment configuration scripts must finish running in 45 minutes or less.
- Configuration script. You can add one or more configuration scripts depending on the number of servers that you select to run scripts during the launch phase.
  - For each pre-deployment configuration script that you want to run, choose to use a script located in Amazon S3 and enter the URL path of the script, or upload a script file.
  - Select the servers to run the pre-deployment configuration scripts during the launch phase. You can choose to run pre-deployment scripts on Primary Application Server (PAS), ABAP System Central Services (ASCS) Server, Database (DB) Server, Additional App Servers (AAS), and Enqueue Replication Server (ERS). You can add a script for each server selected.
  - To remove a configuration script, choose Remove script. To add more configuration scripts, choose Add another script.
Post-deployment configuration script — optional
- Deployment settings. Choose whether to proceed with the deployment if a configuration script fails. If you do not select this option, if the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Post-deployment configuration scripts must finish running in 2 hours or less.
- Configuration script. You can add one or more configuration scripts depending on the number of servers that you select to run scripts during the post-deployment phase.
  - For each post-deployment configuration script that you want to run, choose to use a script located in Amazon S3 and enter the URL path of the script, or upload a script file.
  - Select the servers to run the post-deployment configuration scripts when an EC2 instance has been configured for use. You can choose to run the post-deployment scripts on Primary Application Server (PAS), ABAP System Central Services (ASCS) Server, Database (DB) Server, Additional App Servers (AAS), and Enqueue Replication Server (ERS). You can add a script for each server selected.
  - To remove a configuration script, choose Remove script. To add more configuration scripts, choose Add another script.
After you have entered all of your deployment settings, choose Next.

(See the SAP software installation settings tab.)

SAP software installation settings

On the Configure SAP application software installation page, enter the software installation details for a single instance, distributed instance, or high availability deployment.

SAP application software. Choose whether to install the SAP installation software.
- If you choose No, choose whether to install HANA software. If you want to install HANA software, enter the S3 location for HANA media and the HANA password. Then, proceed to Step 6. If you don't want to install HANA software, proceed to Step 9.
- If you choose Yes, provide the information listed in the following steps.
Application and Version. If you choose to install the SAP application software, select the supported application and version of the software you want to install. The following configuration fields will change based on your application software and version selections. For supported application versions, see SAP applications.
Load balancer for SAP Web Dispatcher. You can select Add Load balancer for SAP Web Dispatcher to launch a load balancer to distribute incoming traffic to your SAP Web Dispatcher instances.
- Load balancer type. Choose the type of load balancer to deploy. For more information, see Load balancers for SAP Web Dispatcher.
- Scheme. Choose whether the load balancer should be internet-facing or intranet-facing. For more information, see Architectures for SAP Web Dispatcher.
- Load balancer secure communication. You can enable this option to configure an HTTPS/TLS listener for your load balancer. This option will terminate the HTTPS/TLS connection at the load balancer. For more information, see Enable HTTPS communication.
  - ACM certificate ARN. Enter the ARN of a certificate in AWS Certificate Manager (ACM) to use for the load balancer HTTPS/TLS listener.
- Availability Zones(AZ) and subnet. The public or private subnets to deploy the load balancer in.
  - Availability Zone 1. Choose the first availability zone to use.
  - Availability Zone 2. Choose the second availability zone to use.
  - Load balancer security group. Choose the security group to assign to the load balancer.
SAP application software location. In order to install the SAP application software, Launch Wizard requires access to the relevant software and files. For instructions to provide Launch Wizard access to the application software and associated files, see Make SAP application software available for AWS Launch Wizard to deploy SAP.
- SAPCAR location. Enter the Amazon S3 path where the SAPCAR is located.
- Software Provisioning Manager (SWPM) location. Enter the Amazon S3 path where the SWPM is located.
- Kernel software location. Enter the Amazon S3 path where the unextracted kernel with media label is located.
- Installation export location. Enter the Amazon S3 path where the installation export is located.
- HANA database software location. Enter the Amazon S3 path where the SAP HANA database software is located.
- SAP HANA client software location. Enter the Amazon S3 path where the SAP HANA client software is located.
Installation details

The following fields may vary according to the application selected.
- Schema name and Master password. Enter the schema name and password to use for the HANA database.
- PAS instance number. Enter the PAS instance number.
- ASCS virtual host name. Enter the ASCS virtual host name used to set up high availability.
- ASCS virtual IP address. Enter the ASCS virtual IP address.
- Enqueue Replication Server (ERS) instance number. Enter the instance number to use for the ERS instance.
- Enqueue Replication Server (ERS) virtual IP address. Enter the virtual IP address used to set up high availability.
- Enqueue Replication Server (ERS) virtual host name. Enter the virtual host name used to set up high availability.
- ASCS instance number. Enter the ASCS instance number.
- Database installation. Choose whether or not to install the HANA database.
- Database virtual host name. Enter the database virtual host name used to set up high availability.
- Software. Select the software type that you want to install. You can install SQL or SAP software.
- Host name. Enter the Central Instance, ASCS, ASCS virtual IP, or Enqueue Replication Server (ERS) host name.
Additional installation details. Select the parameter name and values to use for your software installation. The following fields may vary according to the application selected.
- Number of batch processes. Enter the maximum number of batch processes.
- Number of dialog processes. Enter the maximum number of dialog processes.
- UID for SAP host agent. Enter the UID for the SAP host agent.
- Create a DBA Cockpit user. Choose whether to create a DBA Cockpit user.
AWS Backint Agent. Select the check box to install AWS Backint Agent. For more information, see AWS Backint Agent for SAP HANA.
1. S3 file path. Select or enter the Amazon S3 location to store the SAP HANA backup files.
2. AWS KMS key ARN. Select the ARN of the KMS key that can be used by AWS Backint Agent to encrypt the backup files. For more information, see the AWS Backint Agent for SAP documentation.
3. Agent version. Select the AWS Backint Agent version you want to install.
Additional preferences.
1. When you use AWS Backint Agent, the HANA backup files are stored in Amazon S3, which eliminates the requirement for local EBS backup volumes. If you want Launch Wizard to provision local EBS backup volumes for file-based backups that can be configured manually after deployments, select the check box.
2. By default, a Launch Wizard deployment rolls back when the AWS Backint Agent installation fails. If you want to continue with a Launch Wizard deployment when the AWS Backint Agent installation fails, select the check box. This option does not apply to high availability deployments.
IAM permissions. To deploy an application successfully, Launch Wizard must be allowed to perform operations in other AWS services on your behalf. To do this, the Launch Wizard IAM role, AmazonEC2RoleForLaunchWizard, must have permissions attached to perform these operations, which include AWS Backint Agent operations, running pre- and post-deployment configuration scripts, and downloading the SAP installation media from Amazon S3. If the required policy is not attached to the Launch Wizard role, the Launch Wizard deployment can fail. Select the check box to verify that you have attached the required permissions before deploying.

For steps to attach the required permissions to AmazonEC2RoleForLaunchWizard, see AWS Identity and Access Management (IAM) in this guide.
Choose Deploy

(See the Review tab)

Review

On the Review page, review your infrastructure, application, and deployment model settings. If you are satisfied with your selections, choose Deploy. If you want to change settings, choose Previous.
When you choose Deploy, you are redirected to the Deployments page, where you can view the status of your deployment, and also the deployment details.

SAP HANA database

Application settings

On the Configure application settings page, enter your SAP HANA database application settings.

Application type. Select SAP HANA database. This configuration includes:
- EC2 instances for an SAP HANA database
- Optional installation of SAP HANA database software
General Settings – SAP HANA. Enter the settings for your SAP HANA database installation.
- SAP HANA System ID (SID). Enter the SAP HANA system ID for your system. The HANASID must be different from SAPSID if you are configuring a single instance deployment.
- SAP HANA Instance number. Enter the instance number to use for your SAP HANA system. This must be a two-digit number from 00 through 99.
- EBS Volume Type for SAP HANA. Select the EBS volume types that you want to use for SAP HANA Data, SAP HANA Logs, and SAP Others from the dropdown lists.
  
  Note
  gp3 volumes are not supported for HANA production databases running on Xen instances (X1, X1e, R4, and R3). When you deploy HANA databases with Xen instances after choosing Production as the Deployment environment under the Configuration options, gp2 volumes will be used to set up SAP HANA Data and Logs on the instances you selected for the HANA database.
- Select Make this selection to use Amazon FSx for NetApp ONTAP for all SAP HANA database file systems, except root, backup, and media file systems.
  
  Your chosen Amazon EBS volume type is used for the application layer.
- SAP HANA software install. Select whether you want to download the SAP HANA software.
  - If you select Yes, enter the Amazon S3 location where the SAP HANA software is located. The S3 bucket must have the prefix “launchwizard” in the bucket name to ensure that the Launch Wizard IAM role policy for EC2 has read-only access to the bucket. For steps to set up the folder structure for your S3 bucket, see Make SAP HANA software available for AWS Launch Wizard to deploy a HANA database. Enter a password to use for your SAP HANA installation.
    
    AWS Backint Agent. Select the check box if you want to deploy AWS Backint Agent for backup and recover along with the application. For more information about AWS Backint Agent, see AWS Backint Agent for SAP HANA.
    
    S3 URI. Enter the URI of the S3 bucket where you want to store your SAP HANA backup files. For example, s3://<bucket-name>.
    
    S3 Encryption (AWS KMS key ARN). Select the ARN of the KMS key that AWS Backint Agent can use to encrypt the backup files stored in your Amazon S3 bucket.
    
    Agent version. Select the version number of the agent that you want to install. If you do not enter a version number, the latest published version of the agent is installed.
    
    Additional Backint preferences.
    
    If you selected to use AWS Backint agent, the agent backs up files to S3, which removes the requirement for EBS backup volumes. Select this check box to provision local EBS backup volumes for file-level backups.
    
    By default, Launch Wizard rolls back a deployment when the AWS Backint Agent installation fails. Select the check box if you want Launch Wizard to continue with non-HA application deployments when the Backint installation fails.
    
    Verify that you have attached the required policy for Backint operations to the following role. Select this check box after you have attached the required policy to the AmazonEC2RoleForLaunchWizard. This policy allows Launch Wizard to perform Backint Agent operations on your behalf. The policy and instructions to attach the policy to the role are provided by Launch Wizard during deployment. This information can also be found in Step 2 of the Backint Agent IAM documentation.
  - If you select No, only the AWS infrastructure is provisioned so you can manually deploy an SAP HANA database post deployment .
After you enter your application settings, choose Next.

(Use the tab for Single instance deployment, Multiple instance deployment, or High availability deployment, depending on your configuration)

Single instance deployment

On the Configure deployment model page, enter the deployment details for the SAP HANA database deployment.

Deployment model. Launch Wizard supports single instance deployments, multiple instance deployments, and high availability deployments. Select Single instance deployment.
Settings for SAP HANA database on one instance
- Instance details.
  - Under Image type, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the ERS instance.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
  - Host name. Enter the host name for the EC2 instance.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
- Under Instance sizing, choose Use AWS recommended resources or Choose your instance.
  Use AWS recommended resources.
  
  Define requirements. Choose the requirements for your recommended resources from the dropdown list.
  
  Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
  
  SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  Choose your instance.
  
  Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include applicable taxes or discounts.
- Under Amazon FSx for NetApp ONTAP storage, enter your desired volume sizes for SAP HANA data, log, and other file systems. The displayed default values are based on your selection of the instance type.
Pre- and post-deployment configuration scripts — optional

You can run pre- and post-deployment configuration scripts during application provisioning. For more information about how Launch Wizard accesses and deploys these scripts, see Custom deployment configuration scripts.
Pre-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Pre-deployment configuration scripts must finish running in 45 minutes or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
Post-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Post-deployment configuration scripts must finish running in 2 hours or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
After you enter your deployment settings, choose Next.

(See the Review tab)

Multiple instance deployment

On the Configure deployment model page, enter the deployment details for the SAP HANA database deployment.

Deployment model. Launch Wizard supports single instance deployments, multiple instance deployments, and high availability deployments. Select Multiple instance deployment.
SAP HANA on multiple EC2 instances
- Instance details.
  - Under Instance sizing, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
    
    Operating System. Select a supported operating system version for the SAP HANA servers.
    
    AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
- Under Instance sizing, choose Use AWS recommended resources or Choose your instance.
  Use AWS recommended resources.
  
  Infrastructure requirements. Choose the requirements for your recommended resources from the dropdown list.
  
  Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
  
  SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  Choose your instance.
  
  Instance type. Choose the instance type from the dropdown list.
  - Host Name for SAP system. Enter the host name for the EC2 instance.
  - Number of worker nodes. Enter the number of EC2 instances to be configured as worker nodes for this SAP HANA system.
  - Worker node hostname prefix. Enter the hostname prefix for the worker nodes.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
  - Recommended Resources. Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include applicable taxes or discounts.
- Under Amazon FSx for NetApp ONTAP storage, enter your desired volume sizes for SAP HANA data, log, and other file systems. The displayed default values are based on your selection of the instance type.
Pre- and post-deployment configuration scripts — optional

You can run pre- and post-deployment configuration scripts during application provisioning. For more information about how Launch Wizard accesses and deploys these scripts, see Custom deployment configuration scripts.
Pre-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Pre-deployment configuration scripts must finish running in 45 minutes or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
Post-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Post-deployment configuration scripts must finish running in 2 hours or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
After you enter your deployment settings, choose Next.

(See Review tab)

High availability deployment

On the Configure deployment model page, enter the deployment details for the SAP HANA database deployment.

Deployment model. Launch Wizard supports single instance deployments, multiple instance deployments, and high availability deployments. Select High availability deployment.
Instance details.
- Under Instance details, choose whether to use AWS/Marketplace/Community images or Bring your own images (BYOI).
  - Operating System. Select a supported operating system version for the SAP HANA servers.
  - AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
- Primary and secondary instance details. Enter details for both the primary and secondary instances.
  - SAP HANA host name. Enter the host name for the SAP HANA primary and secondary instances.
  - Server site name. Enter the primary and secondary site name for the SAP HANA system replication.
- Overlay IP address. Enter the overlay IP address to assign to the active node. The IP address should be outside of the VPC CIDR and must not be used by any other HA cluster. It is configured to always point to the active SAP HANA node.
- Pacemaker tag name. Enter the tag to assign to each EC2 instance. This tag is used by the pacemaker component of SLES HAE and RHEL for SAP high availability solutions and must not be used by any other EC2 instance in your account.
- Under Instance sizing, choose Use AWS recommended resources or Choose your instance.
  Use AWS recommended resources.
  
  Infrastructure requirements. Choose the requirements for your recommended resources from the dropdown list.
  
  Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
  
  SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  Choose your instance.
  
  Instance type. Choose the instance type from the dropdown list.
  - Recommended Resources. Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections. This is an estimate of AWS costs to deploy additional resources and does not include applicable taxes or discounts.
- Under Amazon FSx for NetApp ONTAP storage, enter your desired volume sizes for SAP HANA data, log, and other file systems. The displayed default values are based on your selection of the instance type.
Pre- and post-deployment configuration scripts — optional

You can run pre- and post-deployment configuration scripts during application provisioning. For more information about how Launch Wizard accesses and deploys these scripts, see Custom deployment configuration scripts.
Pre-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Pre-deployment configuration scripts must finish running in 45 minutes or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
Post-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Post-deployment configuration scripts must finish running in 2 hours or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
After you enter your deployment settings, choose Next.

(See Review tab)

Review

On the Review page, review your infrastructure, application, and deployment model settings. If you are satisfied with your selections, choose Deploy . If you want to change settings, choose Previous.
When you choose Deploy , you are redirected to the Deployments page, where you can view the status of your deployment, and also the deployment details.

NetWeaver stack on SAP ASE database

Application settings

On the Configure application settings page, enter your NetWeaver stack on SAP ASE database application settings.

Application type. Select NetWeaver stack on SAP ASE database. This configuration includes:
- NetWeaver stack for a single instance.
- EC2 instances for the NetWeaver application tier
- SAP NetWeaver ABAP or JAVA software install.
General settings – SAP system. Enter the settings for your SAP system.
- SAP Application ID. Select the application you want to deploy from the dropdown. The options include, SAP NetWeaver ABAP, SAP NetWeaver JAVA, and SAP Solution Manager.
- SAP System ID (SAPSID). An identifier for your system. The ID must be a three character, alphanumeric string.
- SAP System Admin User ID. The user ID number for the SAP system admin (<sid>adm). The minimum number is 100, and the maximum allowed number is 65536.
- EBS Volume Type for NetWeaver application stack instances. Choose which volume type to use for the NetWeaver application file system /usr/sap/SAPSID from the dropdown list.
- Transport Domain Controller. Specify whether the SAP system will be the domain controller for the SAP landscape. If not, select the transport file system of the domain controller to be mounted.
General Settings – SAP Adaptive Server Enterprise (ASE). Enter the settings for your SAP ASE database.
- SAP ASE User ID number. Enter the user ID number for the SAP ASE database admin (syb<SAPSID>). The minimum number is 100, and the maximum allowed number is 65536.
- EBS Volume Type for SAP ASE filesystems. Select the EBS volume types to use for SAP ASE Data, SAP ASE Logs, and SAP ASE Backup filesystems from the dropdown lists.
After you enter your application settings, choose Next.

Use the tab for Single instance deployment for further information.

Single instance deployment

On the Configure deployment model page, enter the deployment details for a single instance deployment.

ASCS, PAS, and DB on one EC2 instance. Enter the deployment settings for your instance.
- Instance details.
  - Under Image type, choose whether to use AWS/Marketplace/Community image or Bring your own image (BYOI).
  - Operating System and version. Select a supported operating system version for the ASCS instance. For a complete list of operating system versions supported for ASCS, see Operating systems.
  - AMI ID. For BYOI, select the AMI that you want to use from the dropdown.
  - Host name. Enter the host name for the EC2 instance.
  - Private IP address. Choose whether to use an Auto-assigned (default) IP address or a Custom IP address.
    
    Auto-assign (default). When you select this option, an IP addressed will be assigned for you. This is the default option.
    
    Private IP address. When you select this option, you can enter a single IP address. Verify that this IP address is within the subnet range of the instance you are launching.
  - Auto Recovery. Auto recovery is an Amazon EC2 feature to increase instance availability. Select the check box to enable EC2 automatic recovery for the instance. For more information, see Recover Your Instance in the Amazon EC2 User Guide.
- Instance sizing.
  
  Under Instance sizing type, choose Based on infrastructure requirements or Based on instance type.
  - Use AWS recommended resources.
    
    Infrastructure requirements. Choose the requirements for your recommended resources from the dropdown list.
    
    Based on CPU/Memory. If you select this option, enter the required number of vCPU Cores and Memory. Amazon EC2supports up to 448 logical processors. If the amount of memory required exceeds 4TB, dedicated hosts are required.
    
    SAPS (SAP Application Performance Standard). If you select this option, enter the SAPS rating for the SAP certified instance types.
  - Choose your instance.
    
    Instance type. Choose the instance type from the dropdown list.
- Storage Sizing. Enter the size, IOPS, and throughput for the data, log, and backup filesystems. You can have upto 6 data filesystems, 1 log filesystem, and 1 backup filesystem.
- Recommended Resources. AWS Launch Wizard displays the Estimated monthly cost of operation based on your instance sizing selections and the EBS volumes that will be created and attached to the launched instances. This is an estimate of AWS costs to deploy additional resources and does not include any image costs, EC2 reservations, applicable taxes, or discounts.
Pre- and post-deployment configuration scripts — optional

You can run pre- and post-deployment configuration scripts during application provisioning. For more information about how Launch Wizard accesses and deploys these scripts, see Custom deployment configuration scripts.
Pre-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Pre-deployment configuration scripts must finish running in 45 minutes or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
Post-deployment configuration script — optional
- Deployment settings. In the event of a configuration script failure or time out, select whether to ignore all failures and proceed with the deployment. If you do not select this option, when the configuration scripts fail or time out, Launch Wizard will roll back the workload and delete all of the AWS resources created by Launch Wizard. Post-deployment configuration scripts must finish running in 2 hours or less.
- Configuration script. Choose to use a script located in Amazon S3 and enter the URL path of the script, or enter a script manually by uploading a script file. To remove the configuration script, choose Remove script.
After you have entered your deployment settings, choose Next.

See the SAP software installation settings tab for further information.

SAP software installation settings

On the Configure SAP application software installation page, enter the software installation details for a single instance.

SAP application software. Choose whether to install the SAP installation software.

If you choose Yes, provide the information listed in the following steps.
Application and Version. If you choose to install the SAP application software, select the supported application and version of the software you want to install. The following configuration fields will change based on your application software and version selections. For supported application versions, see SAP applications.
SAP application software location. In order to install the SAP application software, Launch Wizard requires access to the relevant software and files. For instructions to provide Launch Wizard access to the application software and associated files, see Make SAP application software available for AWS Launch Wizard to deploy SAP.
- SAPCAR location. Enter the Amazon S3 path where the SAPCAR is located.
- Software Provisioning Manager (SWPM) location. Enter the Amazon S3 path where the SWPM is located.
- Kernel software location. Enter the Amazon S3 path where the unextracted kernel with media label is located.
- Installation export location. Enter the Amazon S3 path where the installation export is located.
- SAP ASE database software location. Enter the Amazon S3 path where the SAP ASE database software is located.
Installation details

The following fields may vary according to the application selected.
- Master password. Enter the password to use for the SAP ASE database.
- PAS instance number. Enter the PAS instance number.
- ASCS instance number. Enter the ASCS instance number.
Additional installation details. Select the parameter name and values to use for your software installation. The following fields may vary according to the application selected.
- Number of batch processes. Enter the maximum number of batch processes.
- Number of dialog processes. Enter the maximum number of dialog processes.
- UID for SAP host agent. Enter the UID for the SAP host agent.
IAM permissions. To deploy an application successfully, Launch Wizard must be allowed to perform operations in other AWS services on your behalf. To do this, the Launch Wizard IAM role, AmazonEC2RoleForLaunchWizard, must have permissions attached to perform these operations, which include AWS Backint Agent operations, running pre- and post-deployment configuration scripts, and downloading the SAP installation media from Amazon S3. If the required policy is not attached to the Launch Wizard role, the Launch Wizard deployment can fail. Select the check box to verify that you have attached the required permissions before deploying.

For steps to attach the required permissions to AmazonEC2RoleForLaunchWizard, see AWS Identity and Access Management (IAM) in this guide.
Choose Deploy

See the Review tab for futher information.

Review

On the Review page, review your infrastructure, application, and deployment model settings. If you are satisfied with your selections, choose Deploy. If you want to change settings, choose Previous.
When you choose Deploy, you are redirected to the Deployments page, where you can view the status of your deployment, and also the deployment details.

Clone deployment

You can now clone your SAP deployments created after April 21, 2022.

Sign in to https://console.aws.amazon.com/launchwizard.
In the Deployments pane on the left, select SAP.
Choose an existing deployment from the list of deployments and select Actions > Clone deployment.

Cloning inputs

With a cloned deployment, the following inputs must be provided.

Enter a unique name for the cloned deployment.
For SAP landscape infrastructure, you must define the configuration type.
- You can Create new configuration by entering a new Configuration name and checking the Verify connectivity box.
- To use the same configuration, select Apply saved configuration and choose a configuration from the list.
The application and database credentials are not carried over. Enter your application and database passwords when prompted.

Warning Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Document Conventions

Deploy an application with Launch Wizard

Deploying an SAP application (AWS CLI)

Deploying an SAP application (Console)

Topics

Access AWS Launch Wizard

Deploy an SAP application with AWS Launch Wizard

Create a deployment

Define infrastructure

Important

To create a private subnet

Default NO_PROXY URL details

Note

Application and deployment settings

Topics

NetWeaver stack on SAP HANA database

Note

Pre- and post-deployment configuration scripts — optional

Pre-deployment configuration script — optional

Post-deployment configuration script — optional

Pre- and post-deployment configuration scripts — optional

Pre-deployment configuration script — optional

Post-deployment configuration script — optional

Private IP address settings

Pre- and post-deployment configuration scripts — optional

Pre-deployment configuration script — optional

Post-deployment configuration script — optional

Installation details

Additional preferences.

SAP HANA database

Note

Pre- and post-deployment configuration scripts — optional

Pre-deployment configuration script — optional

Post-deployment configuration script — optional

SAP HANA on multiple EC2 instances

Pre- and post-deployment configuration scripts — optional

Pre-deployment configuration script — optional

Post-deployment configuration script — optional

Pre- and post-deployment configuration scripts — optional

Pre-deployment configuration script — optional

Post-deployment configuration script — optional

NetWeaver stack on SAP ASE database

Pre- and post-deployment configuration scripts — optional

Pre-deployment configuration script — optional

Post-deployment configuration script — optional

Installation details

Clone deployment

Cloning inputs

Default `NO_PROXY` URL details