Technical requirements - SAP NetWeaver on Amazon
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Technical requirements

The following requirements must be completed before starting the SAP installation and the high availability cluster implementation:

  • Ensure that you have the information described in the following table for your existing Amazon resources:

Information Description
Amazon Region Region where you want to deploy your Amazon resources.
Availability Zone (AZ) Availability Zone within your target Region where you want to deploy your resources. To follow the instructions in this guide, you need two Availability Zones.
Amazon VPC id Amazon VPC where you want to deploy your Amazon EC2 instances for SAP installation.
VPS subnet id Subnet where you want to deploy your Amazon EC2 instances.
Linux AMI id Amazon Machine Image (AMI) that will be used to launch your Amazon EC2 instances. For more information, see Operating systems for SAP NetWeaver HA.
Key pair Make sure that you have generated the key pair in your target Region and that you have access to the private key.
Security group id Name of the security group that you want to assign to your Amazon EC2 instances.
Amazon EFS Amazon EFS filesystem id and DNS name that will be used in the high availability cluster configuration.
  • You must have permissions to modify route tables in the Amazon EC2 instances that you will use.

  • Ensure that the cluster package level and the installed Amazon CLI is the same for both participating nodes.

  • The Security Group attached to both cluster nodes should allow inbound UDP traffic on port 5405.

  • Both cluster nodes should be able to connect to the Amazon EC2 API endpoint through an internet connection or a VPC endpoint.

  • The Amazon user with permissions to:

    • Modify Amazon VPC route tables

    • Modify Amazon EC2 instance properties

    • Create IAM policies and IAM roles

    • Create Amazon EFS filesystems

  • To ensure that restarts are predictable, we recommend disabling simplified automatic recovery and not configuring Amazon CloudWatch action based recovery for instances that are part of a pacemaker cluster. Use the following command to disable simplified automatic recovery.

    aws ec2 modify-instance-maintenance-options --instance-id i-0abcdef1234567890 --auto-recovery disabled
  • You must ensure that stop protection is disabled for Amazon EC2 instances that are part of a pacemaker cluster. Use the following command to disable stop protection.

    aws ec2 modify-instance-attribute --instance-id i-1234567890abcdef0 --no-disable-api-stop
  • The user must have root user credentials at OS level on the cluster nodes.

The following values are used to configure HSR and high availability cluster in the example used in this guide:

ASCS Physical Hostname hahost01
ASCS Virtual Hostname ascshost
ERS Physical Hostname hahost02
ERS Virtual Hostname ershost
ASCS Instance Number 00
ERS Instance Number 10