SAP HANA Quick Start

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.

This Quick Start supports the performance-optimized scenario.

The Quick Start follows security best practices by establishing 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.

The Multi-AZ, single-node, high availability setup is based on SAP Note 2309342SUSE Linux Enterprise High Availability Extension on AWS for SAP HANA.

        Multi-AZ, single-node, high availability architecture for SAP HANA on AWS

Figure 3: Multi-AZ, single-node, high availability architecture for SAP HANA on AWS