SAP HANA is an in-memory relational database and application platform that provides high-performance analytics and real-time data processing.

The AWS Cloud provides a suite of infrastructure services that enable you to deploy SAP HANA in a highly available, fault-tolerant, and affordable way. By deploying this solution on the AWS Cloud, you can take advantage of the functionality of SAP HANA along with the flexibility and security of AWS.

AWS Services

1. Amazon VPC — The Amazon Virtual Private Cloud (Amazon VPC) service lets you provision a private, isolated section of the AWS Cloud where you can launch AWS services and other resources in a virtual network that you define. You have complete control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways.
2. EC2 — The Amazon Elastic Compute Cloud (Amazon EC2) service enables you to launch virtual machine instances with a variety of operating systems. You can choose from existing AMIs or import your own virtual machine images. 
3. Automatic recovery — Automatic recovery is a feature of Amazon EC2 that is designed to increase instance availability. You can enable automatic recovery for an instance by creating an Amazon CloudWatch alarm that monitors an Amazon EC2 instance and automatically recovers the instance if it becomes impaired due to an underlying hardware failure or a problem that requires AWS involvement to repair. A recovered instance is identical to the original instance, including the instance ID, private IP addresses, Elastic IP addresses, and all instance metadata. This Quick Start optionally enables automatic recovery on SAP HANA nodes for you.
 4. Amazon EBS — Amazon Elastic Block Store (Amazon EBS) provides persistent block level storage volumes for use with EC2 instances in the AWS Cloud. Each EBS volume is automatically replicated within its Availability Zone to protect you from component failure, offering high availability and durability. EBS volumes provide the consistent and low-latency performance needed to run your workloads.
5. AWS CloudFormation — AWS CloudFormation gives you an easy way to create and manage a collection of related AWS resources, and provision and update them in an orderly and predictable way. You use a template to describe all the AWS resources (e.g., EC2 instances) that you want. You don’t have to individually create and configure the resources or figure out dependencies — AWS CloudFormation handles all of that.
6. Amazon CloudWatch — Amazon CloudWatch monitors your AWS resources and the applications you run on AWS in real time. You can use Amazon CloudWatch to collect and track metrics, collect and monitor log files, set alarms, and automatically react to changes in your AWS resources. 7. NAT Gateway — NAT Gateway is an AWS managed service that controls NAT gateway resources. A NAT gateway is a type of network address translation (NAT) device that enables instances in a private subnet to connect to the internet or to other AWS services, but prevents the internet from connecting to those instances. 
8. IAM — AWS Identity and Access Management (IAM) enables you to securely control access to AWS services and resources for your users. With IAM, you can manage users, security credentials such as access keys, and permissions that control which AWS resources users can access, from a central location.
9. AWS CloudTrail — AWS CloudTrail enables governance, compliance, operational auditing, and risk auditing of your AWS account. With CloudTrail, you can log, continuously monitor, and retain account activity related to actions across your AWS infrastructure. You can use CloudTrail trails to deliver CloudTrail events to an S3 bucket.
10. AWS Config — AWS Config is a service that enables you to assess, audit, and evaluate the configurations of your AWS resources. AWS Config continuously monitors and records your AWS resource configurations and allows you to automate the evaluation of recorded configurations against desired configurations. With AWS Config, you can review changes in configurations and relationships between AWS resources, dive into detailed resource configuration histories, and determine your overall compliance against the configurations specified in your internal guidelines. 
11. AWS Lambda — AWS Lambda is a serverless compute service that runs your code in response to events and automatically manages the underlying compute resources for you.

Single-AZ, Single-Node Architecture

The Single-AZ, single-node deployment option provisions a single EC2 instance with your choice of Amazon EBS storage and operating system to host the SAP HANA platform. For best security practices establish a VPC with public and private subnets. For secure access, the SAP HANA server is placed in the private subnet, which is not directly accessible from the internet. You can also install SAP HANA Studio manually in the optional Windows Server instance that is provisioned in the public subnet. For SSH access to the SAP HANA server, you can use the bastion host or an SSH client on the optional Windows Server instance.

Single-AZ,Single node architecture for SAP Hana on AWS
Multi-AZ (HA), Single-Node Architecture

The Multi-AZ (HA), single-node deployment option provisions two EC2 instances in private subnets in two different Availability Zones, with your choice of Amazon EBS storage. This architecture is based on SLES High Availability Extension (HAE), which is part of the SLES for SAP operating system. There are two main scenarios for an SAP HANA high availability deployment: 
Performance-optimized: In this scenario, both primary and secondary nodes have the same size and use synchronous replication mode for SAP HANA System Replication (HSR). The secondary instance is configured to preload tables. 
Cost-optimized: In this scenario, the secondary node can be used for production as well as non-production (for example, QA) work. Before takeover by production, the non production instance running on the secondary node has to be stopped to provide resources for production. In this scenario, you can configure synchronous replication mode; however, table preload needs to be switched off on the secondary node.

Multi-AZ,Single node architecture for SAP Hana on AWS
AWS Instance Type for SAP HANA

u-6tb1.metal, u-9tb1.metal, and u-12tb1.metal
x1.16xlarge, x1.32xlarge, x1e.xlarge*, x1e.2xlarge*, x1e.4xlarge*, and x1e.32xlarge
r3.2xlarge*, r3.4xlarge*, and r3.8xlarge
r4.2xlarge* (default), r4.4xlarge*, r4.8xlarge, and r4.16xlarge

* These instance types aren’t supported for SAP HANA production workloads.