reference deployment


System cluster for NetWeaver-based applications and SAP HANA databases

This Quick Start automatically deploys an SAP S/4HANA environment on the Amazon Web Services (AWS) Cloud. SAP S/4HANA provides a set of technologies for developing and running SAP applications.  

The Quick Start deploys an SAP application tier, an SAP HANA database tier, and, optionally, Remote Desktop Protocol (RDP) and bastion hosts within a virtual private cloud (VPC) in your AWS account. The deployment includes an ABAP SAP Central Services (ASCS) server, a Primary Application Server (PAS) instance that provides SAP system utilities, an optional Additional Application Server (AAS) instance, and AWS core infrastructure services to scale out the SAP application tier.



This Quick Start was developed by
AWS solutions architects, cloud support engineers,
and SAP consultants.

  •  What you'll build
  •  How to deploy
  •  Cost and licenses
  •  What you'll build
  • Use this Quick Start to deploy and configure the following in your AWS account:

    • A highly available architecture that spans two Availability Zones.*
    • A VPC configured with public and private subnets according to AWS best practices. This provides the network infrastructure for your deployment.*
    • In the public subnets, managed network address translation (NAT) gateways to allow outbound internet access for the SAP instances in the private subnets.*
    • Optional resources deployed in the public subnets:
      • An optional Linux bastion host in an Auto Scaling group to allow inbound Secure Shell (SSH) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in the private subnets.*
      • An optional Remote Desktop Protocol (RDP) Windows Server to host SAP GUI and third-party front-end applications for managing SAP systems in the private subnets.  
    • Resources deployed in the private subnets:
      • Multiple Amazon EC2 instances to host the HANA database and the S/4HANA ASCS, PAS, and an optional AAS. For standard and distributed installation options, see the deployment guide.
      • Directory /sapmnt, built on a Network File System (NFS) or on Amazon Elastic File System (Amazon EFS) for SAP file sharing among all S/4HANA instances.
      • For multiple-node HANA database deployment, an NFS mounted on directory /usr/sap for file sharing among all HANA database server nodes.
      • An optional automated installation of SAP S/4HANA and SAP HANA.
    • An Identity and Access Management (IAM) role for access to necessary AWS services by the deployment processes.
    • Three security groups for restricted inbound access from the optional bastion host, between the database instances, and for application access to the database.
    • AWS Command Line Interface (AWS CLI) and an instance role for accessing installation software in the Amazon Simple Storage Service (Amazon S3) bucket.
    • A dedicated Amazon Route 53 private hosted zone to host the HANA database and S/4HANA server names.

    This Quick Start supports the SUSE Linux Enterprise Server (SLES) operating system for the SAP S/4HANA instances. SAP HANA is supported with your choice of Linux operating systems: SLES, SLES for SAP, or Red Hat Enterprise Linux (RHEL).

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

  •  How to deploy
  • To build your S/4HANA 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
    2. Download, extract, and stage the SAP S/4HANA software.
    3. Launch the Quick Start. Each deployment takes 1.5-2.5 hours. You can choose from two options:
    4. Verify the S/4HANA deployment by accessing the SAP level or the operating system level.

    To customize your deployment, you can configure your AWS infrastructure, enable logging with AWS CloudTrail and AWS Config, and configure SAP S/4HANA and SAP HANA settings such as instance types, storage options, number of nodes, and AAS instances.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.  

  •  Cost and licenses
  • You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.

    The AWS CloudFormation template for this Quick Start includes configuration parameters that you can customize. Some of these settings, such as number of nodes, storage, and instance type, will affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you will be using. Prices are subject to change. 

    Tip   After you deploy the Quick Start, we recommend that you enable the AWS Cost and Usage Report to track costs associated with the Quick Start. This report delivers billing metrics to an S3 bucket in your account. It provides cost estimates based on usage throughout each month, and finalizes the data at the end of the month. For more information about the report, see the AWS documentation.

    This deployment uses a Bring Your Own License (BYOL) model for SAP software. You must already own licenses for SAP, and you must be authorized to download software from the SAP Software Download Center (SWDC).

    For the SAP S/4HANA deployment, this Quick Start launches the Amazon Machine Image (AMI) for the version of the SLES operating system you choose: SLES 12, SLES 12 SP1, SLES 12 SP2, or SLES 12 SP3. The AMI includes the license for the SLES operating system.

    For the SAP HANA deployment, the Quick Start launches the AMI for the operating system you choose (SLES, SLES for SAP, or RHEL), 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 AMIs.