Menu
SAP HANA on AWS
Quick Start Reference Deployment Guide

Planning the Deployment

Before you deploy SAP HANA on AWS, please review the following sections for guidelines on instance types, storage, memory sizing, and operating system choices for deployment.

AWS Instance Types for SAP HANA

This Quick Start supports the following instance types for the SAP HANA host:

  • x1.16xlarge, x1.32xlarge, and x1e.32xlarge

  • x1.32xlarge

  • r3.2xlarge, r3.4xlarge, and r3.8xlarge

  • r4.2xlarge (default), r4.4xlarge, r4.8xlarge, and r4.16xlarge

The default instance type is r4.2xlarge, but you can switch to one of the other types during deployment. The r3.8xlarge, r4.8xlarge, r4.16xlarge, x1.16xlarge, x1.32xlarge, and x1e.32xlarge instance types are officially supported by SAP for production use. For more information about different instance types and their use cases, see the Amazon EC2 Instances webpage.

Storage Configuration for SAP HANA

SAP HANA stores and processes all or most of its data in memory, and provides protection against data loss by saving the data in persistent storage locations. To achieve optimal performance, the storage solution used for SAP HANA data and log volumes should meet SAP's storage KPI. AWS has worked with SAP to certify both Amazon EBS General Purpose SSD (gp2) and Provisioned IOPS SSD (io1) storage solutions for SAP HANA workloads with the configuration shown in the tables provided in this section.

gp2 volumes balance price and performance for a wide variety of workloads, while io1 volumes provide the highest performance consistently for mission-critical applications. With these two options, you can choose the right storage solution that meets your performance and cost requirements. We recommend using the io1 configuration with the X1 instance types for your mission-critical SAP HANA workloads for production use.

Note that only x1e.32xlarge, x1.32xlarge, x1.16xlarge, r4.8xlarge, r4.16xlarge, and r3.8xlarge instances are certified for production use; you can use all the instance types supported by this Quick Start for non-production use.

For multi-node deployments, storage volumes for SAP HANA data and logs are provisioned in the master node and every worker node.

In the following configurations, we intentionally kept the same storage configuration for SAP HANA data/log volumes for all R3 and certain R4 instance types to give you the flexibility to scale up from smaller instance to large instance without having to reconfigure your storage.

gp2-based storage configuration for SAP HANA data and logs:

Instance type RAM (GiB) General Purpose SSD (gp2) storage (SAP HANA data and log volumes) – striped with LVM Total maximum throughput (MiB/s)* Total baseline IOPS Total burst IOPS
x1e.32xlarge 3904 3 x 2048 GiB 480 18000 N/A
x1.32xlarge 1952 3 x 1024 GiB 480 9000 N/A
x1.16xlarge 976 3 x 700 GiB 480 6300 9000
r4.16xlarge 488 3 x 400 GiB 480 3600 9000
r4.8xlarge 244 3 x 300 GiB 480 2700 9000
r4.4xlarge 122
r4.2xlarge 61
r3.8xlarge 244 3 x 300 GiB 480 2700 9000
r3.4xlarge 122
r3.2xlarge 61

io1-based storage configuration for SAP HANA data and logs:

Instance type RAM (GiB) Provisioned IOPS SSD (io1) storage (SAP HANA data and log volumes) – striped with LVM Total maximum throughput (MiB/s)* Total provisioned IOPS
x1e.32xlarge 3904 3 x 2048 GiB 960 15000
x1.32xlarge 1952 3 x 1024 GiB 960 15000
x1.16xlarge 976 2 x 1024 GiB 640 10000
r4.16xlarge 488 2 x 600 GiB 640 9000
r4.8xlarge 244 2 x 450 GiB 640 9000
r4.4xlarge 122
r4.2xlarge 61
r3.8xlarge 244 2 x 450 GiB 640 9000
r3.4xlarge 122
r3.2xlarge 61

* This value represents the maximum throughput that could be achieved when striping multiple EBS volumes. Actual throughput depends on the instance type. Every instance type has its own Amazon EBS throughput limit. For details, see Amazon EBS-Optimized Instances in the AWS documentation.

In addition to the SAP HANA data and log volumes, all instances deployed by this Quick Start will have the following storage configuration for root, SAP binaries, and SAP HANA shared and backup volumes:

Instance type RAM (GiB) Root volume (gp2) SAP binaries (gp2) SAP HANA shared [1] (gp2) SAP HANA backup [2] (st1)
x1e.32xlarge 3904 1 x 50 GiB 1 x 50 GiB 1 x 1024 GiB 1 x 8192 GiB
x1.32xlarge 1952 1 x 50 GiB 1 x 50 GiB 1 x 1024 GiB 1 x 4096 GiB
x1.16xlarge 976 1 x 50 GiB 1 x 50 GiB 1 x 1024 GiB 1 x 2048 GiB
r4.16xlarge 488 1 x 50 GiB 1 x 50 GiB 1 x 512 GiB 1 x 1024 GiB
r4.8xlarge 244 1 x 50 GiB 1 x 50 GiB 1 x 300 GiB 1 x 1024 GiB
r4.4xlarge 122 1 x 50 GiB 1 x 50 GiB 1 x 300 GiB 1 x 512 GiB
r4.2xlarge 61
r3.8xlarge 244 1 x 50 GiB 1 x 50 GiB 1 x 300 GiB 1 x 1024 GiB
r3.4xlarge 122 1 x 50 GiB 1 x 50 GiB 1 x 300 GiB 1 x 512 GiB
r3.2xlarge 61

Notes

[1] In a multi-node architecture, the SAP HANA shared volume is provisioned only once on the master node.

[2] In a multi-node architecture, the size of the SAP HANA backup volume is multiplied by the number of nodes. The SAP HANA backup volume is provisioned on the master node, and NFS is mounted on the worker nodes.

Storage for SAP HANA backup is configured with Amazon EBS Throughput Optimized HDD (st1) volumes. This volume type provides low-cost magnetic storage designed for large sequential workloads. SAP HANA uses sequential I/O with large blocks to back up the database, so st1 volumes provide a low-cost, high-performance option for this scenario. To learn more about st1 volumes, see Amazon EBS Volume Types in the AWS documentation.

The SAP HANA backup volume size is designed to provide optimal baseline and burst throughput as well as the ability to hold several backup sets. Holding multiple backup sets in the backup volume makes it easier to recover your database if necessary. You may resize your SAP HANA backup volume after initial setup if needed. To learn more about resizing your Amazon EBS volumes, see Expanding the Storage Size of an EBS Volume on Linux in the AWS documentation.

Memory Sizing for Deployment

Before you begin deployment, please consult the SAP documentation listed in this section to determine memory sizing for your needs. This evaluation will help you choose Amazon EC2 instances during deployment. (Note that the links in this section require SAP support portal credentials.)

Note

You can take full advantage of the 3,904 GiB of memory that the X1 instance offers for your production workloads depending on your sizing requirement. For details, see the SAP HANA Hardware Directory.

  • To obtain sizing information for a system that has not yet been implemented, use the SAP QuickSizer. The SAP QuickSizer provides information on both the SAP HANA in-memory database and the SAP NetWeaver application server where applicable.

  • To migrate an existing SAP NetWeaver Business Warehouse system from any database platform to SAP HANA, SAP strongly recommends the new ABAP sizing report for SAP NetWeaver BW, which is described in SAP Note 1736976.

Further sizing information is also available in the SAP HANA Administration Guide and in the following SAP HANA notes:

SAP note Description
1736976 Sizing Report for BW on SAP HANA
1637145 SAP BW on SAP HANA: Sizing SAP In-Memory Database
1702409 HANA DB: Optimal number of scale-out nodes for BW on SAP HANA
1855041 Sizing Recommendation for Master Node in BW-on-HANA
1793345 Sizing for SAP Business Suite on SAP HANA
1872170 Business Suite on SAP HANA memory sizing

Operating System for Deployment

This reference deployment supports the following operating systems and versions for your SAP HANA instance:

  • SLES: SLES 11 SP4, SLES 12, SLES 12 SP1, SLES 12 SP1 for SAP

  • RHEL: RHEL 6.6, RHEL 6.7, and RHEL 7.2

Important

For the X1 instance type, this version of the Quick Start supports only the following deployment options:

– SLES 12 and later versions, RHEL 6.7, and RHEL 7.2 for single-node X1 deployment

– SLES 12 and later versions and RHEL 7.2 for multi-node X1 deployment

Contact us at saphana@amazon.com if you want to use RHEL 6.7 for multi-node X1 deployment.

Note

To learn more about the benefits of using SLES for SAP, see the SUSE product page.

Deployment Scenarios

This guide serves as a reference for customers who are interested in deploying SAP HANA on AWS in a self-service fashion. The AWS CloudFormation template provided with this Quick Start bootstraps the AWS infrastructure and automates the deployment of SAP HANA on the AWS Cloud from scratch. The Quick Start provides two deployment scenarios:

  • Deployment of SAP HANA into a new VPC (end-to-end deployment) builds the VPC, subnets, NAT gateway, security groups, bastion host, and optional Windows Server and SAP HANA server(s) with Amazon EBS.

  • Deployment of SAP HANA into an existing VPC provisions SAP HANA servers in your existing infrastructure.

This Quick Start supports the deployment of SAP HANA on two operating systems: You can choose either SLES or RHEL. (See the previous section for supported versions.) The Quick Start also lets you configure additional deployment settings such as CIDR blocks, number of SAP HANA nodes, and Availability Zone, as discussed later in this guide.