AWS for SAP

Amazon Web Services Can Now Support SAP Business Warehouse (BW) Workloads on SAP HANA up to 4TB

AWS has worked with SAP to certify additional scale out architectures for SAP Business Warehouse on HANA and can now support workloads requiring up to 4TB of memory. This sets the record for SAP HANA scale-out nodes in the cloud, and validates AWS is an ideal solution for enterprise customers to cost effectively run SAP HANA. Customers now have the ability to experience all the benefits of HANA analytics while utilizing the agility, cost savings, security and reliability the AWS cloud provides. AWS offers a comprehensive, end-to-end portfolio of cloud computing services to help manage analytics by reducing costs, scaling to meet demand, and increasing the speed of innovation.

Dynamically Scale-out to Meet Demand and Increasing Data Volumes
Customers can now to scale out their AWS infrastructure to support up to 17 HANA nodes* using the AWS r3.8xlarge instance type with 244GiB of RAM. This gives customers the ability to support up to 4TB* of data in memory for Business Warehouse and/or OLAP based HANA workloads. Additionally, AWS has developed the SAP HANA on AWS Quick Start Reference Deployment, which is a step-by-step guide for deploying SAP HANA on AWS in an SAP supported manner. This guide includes field-tested best practices and links to AWS CloudFormation templates, which automate the provisioning of the AWS infrastructure components as well as the SAP HANA deployment.. By utilizing these templates, customers can have a production ready AWS SAP HANA environment up and running in as little as 30 minutes.

SAP HANA Secure Back-up and Recovery Options with Amazon S3
SAP HANA on AWS leverages Amazon Elastic Block Storage (EBS) as the primary means of storage for the HANA database. These SSD-backed EBS volumes are automatically replicated within Availability Zones to protect from component failure, offering high availability and durability. Customers also have the ability to back-up their HANA database to Amazon Simple Storage Services (S3), which is designed to provide 99.999999999% durability for as little as $.03 per GB per month. When customers store any object in Amazon S3, the data is automatically replicated amongst multiple facilities and on multiple devices within each facility in the selected AWS region. Furthermore, Amazon S3 also supports SSL encryption in transit and 256-bit AES encryption at rest, which can be automatically configured.

Replicate SAP HANA Systems in Multiple Availability Zones
When building out any system on AWS it is a best practice to start by configuring your Amazon Virtual Private Cloud (VPC). Amazon VPC allows you to logically isolate your AWS resources within a virtual network you define. You have the ability to completely control the rules within this virtual network, including IP address range, subnets, route tables and gateways. Amazon VPCs can be applied across multiple Availability Zones within a given region. Once the VPC is created, customers can provision their HANA instances within that VPC in multiple Availability Zones within the same region. This allows customers to reduce their single points of failure by replicating their HANA database clusters in multiple Availability Zones using a single VPC

AWS Enterprise Accelerator
Finally, AWS provides its customers with a number of self-service guides on how to deploy SAP HANA at scale on AWS. AWS Professional Services has developed an Enterprise Accelerator program to help customers’ jumpstart their migration of SAP workloads onto the AWS platform. The program includes AWS workshops for SAP, SAP implementation/migrations plans, reference architecture development, and more. Click here to learn more.
*HANA scale-out clusters larger than 5 nodes are currently in controlled availability. SAP will need to verify your BW sizing report result before you implement a HANA scale-out cluster larger than 5 nodes on AWS. Please contact SAP att HWC@sap.com and sap-on-aws@amazon.com before you implement HANA scale-out clusters of this size.

Refer to SAP OSS Note 1964437