Skip to Content
Technical Articles
Author's profile photo Toru Nakayama

Deploying SAP with AWS Launch Wizard using Amazon FSx for NetApp ONTAP volumes

What is the benefits to deploy SAP with AWS Launch Wizard using Amazon FSx for NetApp ONTAP volumes?

Amazon FSx for NetApp ONTAP is AWS fully managed shared storage that provides general data access and management capabilities for ONTAP. The AWS Launch Wizard allows us to deploy your SAP system using Amazon FSx for NetApp ONTAP volumes. This blog describes the steps to deploy an SAP system using Amazon FSx for NetApp ONTAP volumes with AWS Launch Wizard.

This blog refers to AWS user guide for AWS Launch Wizard for SAP.

AWS Launch Wizard for SAP which has been released in November 2022 enables automated deployment and configuration of Amazon FSx for NetApp ONTAP volumes to run SAP HANA data, logs, shares, and kernel file systems.

 

Prerequisites for deploying SAP systems with AWS Launch Wizard for SAP

We need to meet the prerequisites before running AWS Launch Wizard for SAP.

 

Deployment of SAP with AWS Launch Wizard using Amazon FSx for NetApp ONTAP volumes

At first log into our AWS management console, select AWS Launch Wizard, and select SAP under the deployment section within the left pane.

Figure 1 * Click to enlarge

 

From here we can create a new deployment.

Figure 2 * Click to enlarge

 

In step 1, we can define SAP infrastructure. When the “Review Permissions” screen appears, verify that we have the appropriate permissions and click the “Next” button.

Figure 3 * Click to enlarge

 

Next in Step 2, provide the inputs like deployment name, and description which will be assigned to all of the resources that are created by AWS Launch Wizard.

Figure 4 * Click to enlarge

 

Check off “Exports AWS CloudFormation templates and creates an AWS Service Catalog product for this deployment” in the “Create AWS Service Catalog product” section.
It is useful for redeploying the same configuration to create an AWS Service Catalog product from the AWS CloudFormation templates and application configuration scripts created by this Launch Wizard deployment.

If we check off “Exports AWS CloudFormation templates and creates an AWS Service Catalog product for this deployment”, specify the S3 file path to store the AWS CloudFormation templates.

Figure 5 * Click to enlarge

 

Provide all the needed infrastructure details. Create a new configuration, provide a new configuration name, and select whether it’s a production or non-production deployment.

Figure 6 * Click to enlarge

 

Choose EC2 key pair. If you have not previously created a key pair, you can do so by clicking on the “Create key pair name” link.

Choose the VPC and subnet where the SAP instance will be deployed. Choose two Availability Zones (AZs) and at least one private subnet per AZ.

Check off the “Verify connectivity” in order to download the patches from the internet.

Figure 7 * Click to enlarge

 

Create new security groups or choose from existing security groups for both application servers and database servers, and specify IP address and security groups for the external access.

And we can add a proxy server detail if we want.

Figure 8 * Click to enlarge

 

Then choose a timezone, EBS encryption or not, domain name for SAP servers, input an SAPSYS Group ID, and provide SNS topic if we want to receive notifications about the deployment.

Figure 9 * Click to enlarge

 

Then click the “Next” button.

Figure 10 * Click to enlarge

 

Next in Step 3, configure application settings. I am going to deploy an SAP NetWeaver stack in this example, however we can also deploy just HANA database.

Figure 11 * Click to enlarge

 

Here we can input general settings for SAP system such as SAP System ID, SAP System Admin User ID, EBS Volume Type.

In the “Transport Domain Controller” (/usr/sap/trans) section, choose “Yes” (create in new EFS), “No” (use existing EFS and share), or “Not applicable” (standalone and not shared).

Figure 12 * Click to enlarge

 

In the next section, specify the HANA general settings such as HANA System ID, and HANA Instance number.

Check off “Make this selection to use Amazon FSx for NetApp ONTAP for all SAP HANA database file systems, except root, backup, and media file systems.”.

Figure 13 * Click to enlarge

 

If we check it off, the box to choose the EBS volume type for SAP HANA will disappear. Then click the “Next” button.

Figure 14 * Click to enlarge

 

Next in Step 4, we can choose deployment details among Single instance, Distributed instance, or High Availability. I am going to choose Single instance in this case.

Figure 15 * Click to enlarge

 

After that, we can input details about the application and database servers.

Choose the kind of AMI we want to choose if we want to bring our own license or we want to use a license included AMI from AWS Marketplace. An OS subscription must be pre-registered if you want to use an OS offered in the AWS Marketplace, and pick a host name for the installation.

Figure 16 * Click to enlarge

 

Specify the EC2 instance size. Choose “Based on infrastructure requirements” to select the recommended instance type according to the specified vCPU and memory capacity. Choosing “Based on instance type” allows you to manually select an EC2 instance from the list of EC2 instances supported by SAP. In this example, I selected “Based on instance type” and chose “r6i.12xlarge” from the list of EC2 instances supported by SAP for testing.

The disk space for Data/Log/Other in Amazon FSx for NetApp ONTAP storage is automatically set according to the size of the EC2 instance we chose. We can change the disk space as needed based on our sizing requirements.

Figure 17 * Click to enlarge

 

We will also be able to review the monthly estimated cost for the service with an on-demand pricing model. Click the “Next” button after the review.

Figure 18 * Click to enlarge

 

Specify the file path of the SAP installation media previously placed in the S3 bucket.

Figure 19 * Click to enlarge

 

Enter the master password for the user created during installation and confirm the instance number of the SAP system; if using the AWS Backint Agent, choose “Install AWS Backint Agent”.

Figure 20 * Click to enlarge

 

If using AWS Backint Agent, specify the file path of the S3 bucket.

Figure 21 * Click to enlarge

 

Check IAM permissions and click the “Next” button.

Figure 22 * Click to enlarge

 

Next in Step 6, “Review” will be displayed. Review the parameters you entered.

Figure 23 * Click to enlarge

 

Confirm that the parameters entered are correct, and click the “Deploy” button.

Figure 24 * Click to enlarge

 

Deployment is started. Deployment progress can be checked in the Launch Wizard console.

Figure 25 * Click to enlarge

 

These are the procedures where we can deploy SAP with AWS Launch Wizard using Amazon FSx for NetApp ONTAP volumes. Hope this helps to automate deployment and configuration of Amazon FSx for NetApp ONTAP volumes within SAP on AWS environment.

 

Reference

 

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.