Menu
SAP HANA on AWS
Quick Start Reference Deployment Guide

Step 4. Launch the Quick Start

Important

With this reference deployment, you can choose between SUSE Linux Enterprise Server (SLES) and Red Hat Enterprise Linux (RHEL) as the operating system for SAP HANA. If you decide to use RHEL, make sure to complete step 2 first to subscribe to the AMI in the AWS Marketplace. If you decide to choose SLES as the operating system for SAP HANA, no subscriptions are required.

  1. Choose one of the following options to launch the AWS CloudFormation template into your AWS account. For help choosing an option, see the discussion of deployment scenarios earlier in this guide.

    Scenario 1

    Deploy SAP HANA into a new VPC on AWS

    
                                                    Quick Start launch button for SAP HANA in new VPC

    Scenario 2

    Deploy SAP HANA into an existing VPC on AWS

    
                                                    Quick Start launch button for SAP HANA in existing VPC

    Each deployment takes approximately 35-60 minutes to complete, depending on the number of SAP HANA nodes you choose to deploy.

    Note

    You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using this Quick Start. See the Cost and Licenses section for cost estimates. Prices are subject to change. For full details, see the pricing pages for each AWS service you will be using in this Quick Start or the AWS Simple Monthly Calculator.

  2. Check the region that’s displayed in the upper-right corner of the navigation bar, and change it if necessary. This is where the network infrastructure for SAP HANA will be built. By default, the template is launched in the last region you used in your account.

  3. On the Select Template page, keep the default URL for the AWS CloudFormation template, and then choose Next.

  4. On the Specify Details page, change the stack name if needed. Review the parameters for the template. Provide values for the parameters that require input. For all other parameters, review the default settings and customize them as necessary. When you finish reviewing and customizing the parameters, choose Next.

    Parameters are grouped in five major categories. In the following tables, parameters are listed and described separately for the two deployment scenarios:

    Scenario 1: Parameters for deployment into a new VPC

    View template

    Network infrastructure configuration:

    Parameter (label) Default Description
    VPCCIDR (CIDR block of Amazon VPC) 10.0.0.0/16 CIDR block of the VPC to create for the SAP HANA deployment.
    PrivSubCIDR (CIDR block of private subnet) 10.0.1.0/24 CIDR block of the private subnet in the new VPC where SAP HANA will be deployed.
    DMZCIDR (CIDR block of public subnet) 10.0.2.0/24 CIDR block of the public subnet in the new VPC where the managed NAT gateway, bastion host, and RDP instance will be deployed.
    RemoteAccessCIDR (CIDR block for SSH/RDP access) 0.0.0.0/0 CIDR block from where you are likely to access your bastion and RDP instance.
    BASTIONInstanceType (Instance type for bastion host) t2.small EC2 instance type for the bastion host.
    AvailabilityZone (Availability Zone for subnet creation) Depends on region selected (e.g., us-east-1a) Availability Zone where you want to create your subnets.

    Server and storage configuration:

    Parameter (label) Default Description
    MyOS (Operating system and version for SAP HANA) SuseLinux12SP1 Operating system and version to be used for SAP HANA master/worker nodes (see Operating System for Deployment section).
    MyInstanceType (Instance type for SAP HANA) r4.2xlarge EC2 instance type for SAP HANA nodes (see AWS Instance Type for SAP HANA section).
    HostCount (Number of SAP HANA hosts) 1 Total number of nodes you want to deploy in the SAP HANA cluster.
    AutoRecovery (Automatic recovery) Yes Set to No to disable the automatic recovery feature on your SAP HANA nodes.
    KeyName (Key pair) Requires input An existing public/private key pair, which enables you to connect securely to your instance after it launches. When you created an AWS account, this is the key pair you created in your preferred region. This key pair can be used with all EC2 instances launched by the Quick Start.
    VolumeType (Storage volume type) gp2 Amazon EBS storage type to be used for SAP HANA data and log volumes (see Storage Configuration for SAP HANA section).
    Encryption (Encryption) No Set to Yes to enable encryption for all volumes (except root) created for SAP HANA nodes.

    SAP HANA database configuration:

    Parameter (label) Default Description
    DomainName (Domain name) local Name to use for fully qualified domain names.
    HANAMasterHostname (SAP HANA master host name) imdbmaster Host name to use for the SAP HANA master node (DNS short name).
    HANAWorkerHostName (SAP HANA worker host name) imdbworker Host name to use for the SAP HANA worker nodes (DNS short name).

    Note: Depending on the number of nodes, each worker node will have a numeric value appended to it automatically (for example, imdbworker01, imdbworker02, etc.).

    SID (SAP HANA system ID) HDB System ID to be used for HANA installation and setup.
    SAPInstanceNum (SAP HANA instance number) 00 Instance number to be used for SAP HANA installation and setup and to open up specific ports for security groups.
    HANAMasterPass (SAP HANA password) Requires input Password to be used for SAP HANA installation. This password must follow SAP HANA password restrictions.
    HANAInstallMedia (Amazon S3 URL for SAP HANA software) Requires input Full path to Amazon S3 location where you’ve placed the SAP HANA software in step 3.
    InstallHANA (Install SAP HANA software?) Yes Set to No if you don’t want the Quick Start to install SAP HANA during deployment. This (installation) parameter works in conjunction with the previous (URL) parameter. If you leave the URL parameter blank, the Quick Start won’t install the software even if the installation parameter is set to Yes. If you provide a URL but set the installation parameter to No, the Quick Start will stage the SAP HANA software but won’t install it.

    Optional configuration:

    Parameter (label) Default Description
    PlacementGroupName (Placement group name) Name of existing placement group where you want to deploy your SAP HANA cluster. This is required for SAP HANA scale-out deployments only.
    InstallRDPInstance (Windows RDP instance) No Set to Yes to enable the deployment of an Amazon EC2 instance with Windows Server to host SAP HANA Studio.
    RDPInstanceType (Instance type for RDP host) c4.large EC2 instance type for Windows RDP instance.
    Proxy* (URL for Proxy Server) Address of proxy server for HTTP/HTTPS access if you route your Internet traffic via a proxy server (e.g., http://xyz.abc.com:8080 or http://10.x.x.x:8080).

    * The proxy parameter is used only with RHEL operating system deployments.

    Advanced configuration:

    Parameter (label) Default Description
    PrivateBucket (Private bucket) Name of the main build bucket where installation scripts and templates are located. Don’t change this unless directed by AWS Support.

    Scenario 2: Parameters for deployment into an existing VPC

    View template

    Network infrastructure configuration:

    Parameter (label) Default Description
    VPCID (VPC ID) Requires input ID of the existing VPC where you want to deploy your SAP HANA resources.
    HANASubnet (Private subnet) Requires input ID of the private subnet in your existing VPC where you want to deploy SAP HANA instances.
    DMZSubnet (Public subnet) Requires input ID of the public subnet in your existing VPC where you want to deploy the optional RDP instance.
    PrivSubCIDR (CIDR block of private subnet) 10.0.1.0/24* CIDR block of the private subnet in the existing VPC where SAP HANA will be deployed.
    DMZCIDR (CIDR block of public subnet) 10.0.2.0/24* CIDR block of the public subnet in the existing VPC where the bastion host and NAT gateway exist.

    * You can retrieve these values from the previous two parameters (private and public subnet IDs), as shown in Figure 10.

    
                            Finding the Values for the CIDR Block Parameters

    Figure 10: Finding the values for the CIDR block parameters

    Server and storage configuration:

    Parameter (label) Default Description
    MyOS (Operating system and version for SAP HANA) SuseLinux12SP1 Operating system and version to be used for SAP HANA master/worker nodes (see Operating System for Deployment section).
    MyInstanceType (Instance type for SAP HANA) r4.2xlarge EC2 instance type for SAP HANA nodes (see AWS Instance Type for SAP HANA section).
    HostCount (Number of SAP HANA hosts) 1 Total number of nodes you want to deploy in the SAP HANA cluster.
    AutoRecovery (Automatic recovery) Yes Set to No to disable the automatic recovery feature on your SAP HANA nodes.
    KeyName (Key pair) Requires input An existing public/private key pair, which enables you to connect securely to your instance after it launches. When you created an AWS account, this is the key pair you created in your preferred region. This key pair can be used with all Amazon EC2 instances launched by the Quick Start.
    VolumeType (Storage volume type) gp2 Amazon EBS storage type to be used for SAP HANA data and log volumes (see Storage Configuration for SAP HANA section).
    Encryption (Encryption) No Set to Yes to enable encryption for all volumes (except root) created for SAP HANA nodes.

    SAP HANA database configuration:

    Parameter (label) Default Description
    DomainName (Domain name) local Name to use for fully qualified domain names.
    HANAMasterHostname(SAP HANA master host name) imdbmaster Host name to use for the SAP HANA master node (DNS short name).
    HANAWorkerHostname (SAP HANA worker host name) imdbworker Host name to use for the SAP HANA worker nodes (DNS short name).

    Note: Depending on the number of nodes, each worker node will have a numeric value appended to it automatically (for example, imdbworker01, imdbworker02, etc.).

    SID (SAP HANA system ID) HDB System ID to be used for HANA installation and setup.
    SAPInstanceNum (SAP HANA instance number) 00 Instance number to be used for SAP HANA installation and setup and to open up specific ports for security groups.
    HANAMasterPass (SAP HANA password) Requires input Password to be used for SAP HANA installation.
    HANAInstallMedia (Amazon S3 URL for SAP HANA software) Requires input Full path to Amazon S3 location where you’ve placed the SAP HANA software in step 3.
    InstallHANA (Install SAP HANA software?) Yes Set to No if you don’t want the Quick Start to install SAP HANA during deployment. This (installation) parameter works in conjunction with the previous (URL) parameter. If you leave the URL parameter blank, the Quick Start won’t install the software even if the installation parameter is set to Yes. If you provide a URL but set the installation parameter to No, the Quick Start will stage the SAP HANA software but won’t install it.

    Optional configuration:

    Parameter (label) Default Description
    PlacementGroupName (Placement group name) Name of existing placement group where you want to deploy your SAP HANA cluster. This is required for SAP HANA scale-out deployments only.
    InstallRDPInstance (Windows RDP instance) No Set to Yes to enable the deployment of an EC2 instance with Windows Server to host SAP HANA Studio.
    RDPInstanceType (Instance type for RDP host) c4.large EC2 instance type for Windows RDP instance.
    RemoteAccessCIDR (CIDR block for RDP access) 0.0.0.0/0 CIDR block from where you want to access the RDP instance.
    Proxy* (URL for Proxy Server) Address of proxy server for HTTP/HTTPS access if you route your Internet traffic via a proxy server (e.g., http://xyz.abc.com:8080 or http://10.x.x.x:8080).

    * The proxy parameter is used only with RHEL operating system deployments.

    Advanced configuration:

    Parameter (label) Default Description
    PrivateBucket (Private bucket) Name of the main build bucket where installation scripts and templates are located. Don’t change this unless directed by AWS Support.
  5. On the Options page, you can specify tags (key-value pairs) for resources in your stack and set additional options. When you're done, choose Next.

  6. On the Review page, review and confirm the template settings. Under Capabilities, select the checkbox to acknowledge that the template will create IAM resources.

  7. Choose Create to deploy the stack.

  8. Monitor the status of the stack. When the status is CREATE_COMPLETE, you can continue to the next step to verify your deployment.

    
                            Successful Completion of Template Deployment

    Figure 11: Successful completion of template deployment

    The Quick Start creates an Amazon DynamoDB table to track the status of deployment. You can also view the status of your deployment by looking at the contents of the Amazon DynamoDB table from the AWS Management Console.