Automate deployment of SAP systems on ASE database with AWS Launch Wizard

by Chandrasekhar Chittuluru, Ravi Iyer, and Suresh Pulivarthi | on | Permalink |  Share

Automate deployment of SAP systems on ASE database with AWS Launch Wizard

AWS Launch Wizard for SAP is a service that guides you through the sizing, configuration, and deployment of SAP applications on AWS in accordance with AWS, SAP, and operating system vendor best practices.   We are excited to announce that last month, we built on existing capabilities supporting SAP HANA, adding support for automating deployment of SAP systems running on ASE databases. Customers can use AWS Launch Wizard to deploy SAP solutions such as NetWeaver ABAP, Java, and Solution Manager applications onto a single EC2 instance running on an ASE database.

SAP applications can be deployed with Launch Wizard using a console-based experience or APIs.

Getting Started

In this blog we will share details on how to deploy a SAP NetWeaver ABAP system running on an SAP ASE database using AWS Launch Wizard for SAP.

Please complete all the prerequisites before going to the next step.

To get started with an SAP deployment, in the Launch Wizard console, click on Choose Application, select SAP from the Available workloads and click on Create deployment.

Click on Next in the following screen

●        Provide Deployment Name and Infrastructure settings.

The Infrastructure settings of your deployments can be saved based on how you want to classify your deployments. They can then be reused for future SAP systems deployments that share the same infrastructure configuration, for example you have a non-prod and prod configurations used to deploy your non-prod and prod systems respectively. You can save the configurations of your deployments and reuse them later as and when new systems are built or rebuilt that have similar role in the landscape.

●        Choose a key pair to deploy in the SAP instances.

●        Select the Availability Zones and private subnets.

●        Select either assign an existing security groups to the EC2 instances or use the option to Create new security groups to let AWS Launch Wizard create a new ones for your deployment.

●        Ensure Verify connectivity is checked.

●        Provide the Time zone, EBS and DNS details as per your organization requirements

●        Set SAPSYS Group ID

●        Select the option “Create a virtual private IP address and associate a virtual hostname” to associate a virtual private IP address and a virtual hostname to the EC2 instance.

●        Optionally select an Amazon Simple Notification Service (SNS) topic to receive notifications and alerts for the deployment.

●        Click on Next button to configure the application settings.

●        Under Configure application settings select NetWeaver stack on SAP ASE database

Select the type of SAP Application that you plan to deploy on this host using the SAP Application option. Based on this selection, the required AWS resources and operating system will be setup and configured based on best practices.

●        Select “SAP NetWeaver ABAP” as SAP Application.

●        Provide SAPSID and SAP System Admin User ID.

●        Launch Wizard supports two EBS volume types for NetWeaver application stack instances – General Purpose SSD (gp2) and General Purpose SSD (gp3).

●        If the system you plan to deploy is an SAP Transport Domain Controller, select Yes, otherwise No or Not applicable if you don’t want a transport mount to be created on this system.

●        Provide SAP ASE user ID number and Amazon EBS volume type for SAP ASE filesystems.

●        Launch Wizard supports four EBS volume types for SAP ASE Data and Log filesystems: General Purpose SSD (gp2), General Purpose SSD (gp3), Provisioned IOPS SSD (io1) and Provisioned IOPS SSD (io2). The default recommended EBS volume for SAP deployments is gp3, recommendation to go with performance of io2 only if you need a greater number of IOPS than gp3 can provide.  AWS Launch Wizard supports an additional volume type for Backup filesystems: Throughput Optimized HDD (st1) and click on Next

●        Select operating system (SUSE or RHEL) and if you wish to use an AWS provided subscription or Bring your own subscription.

●        Provide the details of Hostname, Virtual host name and private IP address.

●        For Private IP address you have two options now:  Auto-assign IP address (default) and Custom IP address. Select the option Custom IP address if you want to provide your own IP address, else leave the default option of Auto-assign IP address(default).

●        Leave the default option of Auto recovery checked.

●        When you define the Instance sizing, you can either select Based on infrastructure requirements option to let AWS Launch Wizard select a right sized instance for your deployment based on vCPU/Memory requirements you provide or select Based on Instance type to manually choose the instances from the list of SAP supported EC2 instances for your SAP components based on required SAPS.

Option 1: Instance sizing based on Infrastructure requirements

Option 2: Instance sizing based on instance type

●        Provide Storage Sizing information as per your requirements and AWS Launch Wizard shows you the overall cost estimates for the AWS resources that will be provisioned for your deployment.

Use the following options to deploy any custom shell scripts as part of your SAP system deployment.

●        The script provided as part of the Pre-deployment configuration script – optional will be deployed during pre-deployment configuration phase right before the SAP system deployment phase starts.

●        The script provided as part of the Post-deployment configuration script – optional will be deployed during post-deployment configuration phase once SAP system deployment is complete.

●        Visit our public gitHub Repository for automation and personalization scripts tailored to Launch Wizard!

●        Click on Next

●        Provide SAP application details including version of your application, software location, master password for the installation, PAS and ASCS instance numbers.

●        Attach the required policy to the AmazonEC2RoleForLaunchWizard role following the instructions provided in the Instructions hyperlink. Ensure Required policy attached to role is checked before clicking on Next

After reviewing all your configurations, you can deploy your system by clicking Deploy button.

The deployment takes 1 to 2 hours and you will be able to see what infrastructure configuration was used for the deployment, what components of SAP were deployed, and a mapping of SAP components to EC2 instances.

As mentioned earlier in the beginning of this blog, you can also deploy the same system without logging into the AWS console by using AWS Launch Wizard for SAP APIS, see AWS Launch Wizard APIs for more information.

To troubleshoot any issues with AWS Launch Wizard for SAP, refer to the Launch Wizard Troubleshooting Guide.

Note: AWS Launch Wizard will create a set of resources that you are charged for, you can use the Delete deployment option to remove all the resources created as part of the deployment and stop incurring costs.


In this blog, you learned about how to deploy SAP NetWeaver ABAP system based on SAP ASE database using AWS Launch Wizard for SAP console. To learn more, please visit the AWS Launch Wizard Detail Page and documentation.

Note: AWS Launch Wizard will create a set of resources that your charged for and you can use the Delete deployment option to remove the resources and stop incurring costs