Note: The documentation for this SAP HANA Partner Solution (formerly Quick Start) will be deprecated at the end of 2022. The deployment options that are outlined on this page will remain available until April 30, 2023. For an alternative deployment method, refer to AWS Launch Wizard for SAP.

reference deployment


Single-AZ or Multi-AZ configuration, with EC2 instances certified by SAP for production workloads

This Partner Solution deploys SAP HANA systems to the Amazon Web Services (AWS) Cloud, following best practices from AWS and SAP.

SAP HANA is an in-memory relational database and application platform that provides high-performance analytics and real-time data processing. AWS provides SAP customers and partners with an SAP-certified cloud infrastructure to run SAP HANA. The Partner Solution helps to ensure that Amazon Elastic Compute Cloud (Amazon EC2), Amazon Elastic Block Store (Amazon EBS), and the operating system are optimally configured for your SAP HANA system.

This deployment supports the R3, R4, R5, and X1 instance families as well as Amazon EC2 High Memory instances that have 6 TB, 9 TB, 12 TB, 18 TB, and 24 TB of memory, to boost the performance of large-scale, memory-intensive SAP HANA workloads. It also supports both Single-AZ (single-node or multi-node) and Multi-AZ (single-node), high availability configurations.

This Partner Solution is for IT infrastructure architects, administrators, and DevOps professionals who want to customize their own SAP HANA deployment. If you want a more guided deployment option, consider AWS Launch Wizard.

This Partner Solution was developed by AWS.

“Using AWS SAP HANA Partner Solution, we only needed to push a few buttons to get a functioning SAP HANA solution.”

Philip Miller, Director

AWS Service Catalog administrators can add this architecture to their own catalog.  

  •  What you'll build
  • Single-AZ, multinode architecture
    Multi-AZ, single-node architecture with high availability

    The Partner Solution deploys and configures the following components:

    • A virtual private cloud (VPC) configured with public and private subnets. This provides the network infrastructure for your SAP HANA deployment.*
    • An internet gateway to allow access to the internet.*
    • In a public subnet, a bastion host with an Elastic IP address to allow inbound Secure Shell (SSH) access to the EC2 instance(s) that host the SAP HANA database.*
    • A managed network address translation (NAT) gateway to allow outbound internet access for resources in the private subnets.*
    • EC2 instance(s) to host the SAP HANA database, with the appropriate EBS volumes configured to meet or exceed key performance indicators (KPIs) for SAP HANA storage. The Single-AZ configuration gives you a choice of Linux operating system (SLES, SLES for SAP, SLES for SAP BYOS, RHEL for SAP HANA, or RHEL for SAP with High Availability and Update Services). The Multi-AZ configuration supports SLES for SAP and SLES for SAP BYOS.
    • AWS Identity and Access Management (IAM) instance roles with fine-grained permissions for access to the AWS services.
    • Security groups for each instance or function to restrict access to only necessary protocols and ports.
    • An optional, automated installation of SAP HANA software.
    • In a public subnet, an optional EC2 instance with Windows Server to host SAP HANA Studio. You can install SAP HANA Studio manually to administer your SAP HANA database.
    • An optional configuration of AWS CloudTrail trails and AWS Config to help with compliance, audit, and change management requirements.
    • Your choice of Single-AZ (single-node or multi-node), or Multi-AZ, high availability (single-node) configuration.

    * The template that deploys the Partner Solution into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy
  • To build your SAP HANA environment on AWS, follow the instructions in the deployment guide. The deployment process includes these steps:

    1. If you don't already have an AWS account, sign up at and prepare your account.
    2. Subscribe to the operating system image in AWS Marketplace.
    3. Download the SAP HANA software to an Amazon Simple Storage Service (Amazon S3) bucket.
    4. Launch the Partner Solution. The deployment takes 25–60 minutes, depending on the selected configuration. You can choose from these options:
    5. Access SAP HANA nodes on AWS.
    6. Perform testing, backup, and other post-deployment tasks.

    To customize your deployment, you can choose the operating system, choose an instance type for the SAP HANA host, select the number of nodes in a Single-AZ SAP HANA cluster, configure high availability settings for a Multi-AZ setup, and specify additional options.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

  •  Costs and licenses
  • This deployment uses a Bring Your Own License (BYOL) model for SAP HANA. You must already own a license for SAP HANA and have access to the SAP Software Download Center to download the software.

    The Single-AZ deployment option launches the Amazon Machine Image (AMI) for the operating system you choose—SLES, SLES for SAP, SLES for SAP BYOS, RHEL for SAP HANA, or RHEL for SAP with High Availability (HA) and Update Services (US)—and the license cost for the operating system is included in the Amazon EC2 hourly price. There is an additional software cost for SLES for SAP AMI subscriptions in AWS Marketplace. For SLES for SAP BYOS AMIs, you can use your existing, valid subscriptions.

    The Multi-AZ (HA) deployment option is based on the SLES High Availability Extension (HAE), which is included in SLES for SAP; therefore, SLES for SAP is the only operating-system option for Multi-AZ deployment. You must have subscribed to the AWS Marketplace offering for SLES for SAP, or have a registration code (if you choose SLES for SAP BYOS) before you start deployment.

    You are responsible for the cost of the AWS services and any third-party licenses used while running this solution. There is no additional cost for using the solution.

    This solution includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.

    Tip: After you deploy a solution, create AWS Cost and Usage Reports to track associated costs. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, refer to What are AWS Cost and Usage Reports?