Sizing - SAP NetWeaver on AWS


Sizing applies to three key areas - compute, network, and storage.


AWS has certified multiple instance families with different sizes to run SAP workloads. For more details, see Amazon EC2 Instance Types for SAP.

To provision instances based on your requirements, you can use the Right sizing process. This process can help you optimize costs. Although it is ideal to use the right sizing approach when you move your SAP workloads to AWS Cloud, it is an ongoing process. We recommend you to use the latest generation of your selected instance family.

For a greenfield (new) deployment of SAP workloads, you can use the Quick Sizer tool to calculate the compute requirement in SAPS. This helps you to select the closest matching Amazon EC2 instance for a price that is most economical for you. Before completing your selection, ensure that the selected Amazon EC2 instance provides enough Amazon EBS and overall network throughput to meet your application requirements.

For migrations, you can use any of the following data sources to decide the right size of your instance:

  • Source system utilization and workload patterns, such as EarlyWatch alert reports.

  • Source system specification: CPU, memory, storage size + throughput + IOPS, network.

  • Source system SAPS rating.


Network performance is often not explicitly stated as a requirement in SAP sizing. AWS enables you to check the network performance of all Amazon EC2 Instance Types.

Ensure that you have your network components setup to deploy resources related to your SAP workload. If you haven’t already setup network components like Amazon VPC, subnets, route tables etc., you can use the, AWS Quick Start Modular and Scalable VPC Architecture to most effectively deploy scalable Amazon VPC architecture in minutes. After setting up your Amazon VPC, you must set up Amazon EC2 instances within the Amazon VPC for your SAP workloads.


Amazon Elastic Block Store (Amazon EBS) volumes are designed to be highly available and reliable. Amazon EBS volume data is replicated across multiple servers in an Availability Zone to prevent the loss of data from the failure of any single component. Owing to this built-in protection, you can skip configuring RAID 1 for these volumes.

You must check that the storage required is enough to provide sufficient I/O performance. The new gp3 volume is ideal for SAP ASE workloads that require smaller volume size. With gp3, the storage throughput and IOPS are decoupled from the size and can scale independently.

The io2 volume is well-suited for I/O-intensive database workloads that require sustained IOPS performance or more than 16,000 IOPS. The io2 Block Express is another provisioned IOPS SSD volume for workloads that require sub-millisecond latency, sustained IOPS performance, and more than 64,000 IOPS or 1,000 MiB/s of throughput.


io2 Block Express is only supported on select Amazon EC2 instance types. For more information, see Provisioned IOPS SSD volumes.

The following table lists the main directories for SAP ASE database.

Usage Directory
Database instance root files /sybase/<SID>
Database data files /sybase/<SID>/sapdata_1 /sybase/<SID>/sapdata_X
Database log files /sybase<SID>/saplog_1
Database temporary tablespace /sybase/<SID>/saptmp
Diagnostic tablespace for SAPTOOLS /sybase/<SID>/sapdiag
Directory for ASE backup /sybasebackup