Instances and sizing - Databases for SAP applications on AWS
Supported instance typesSizing

Instances and sizing

The following rules and limitations are applicable for deploying SAP applications on AWS using IBM Db2 with FSx for ONTAP.

  • Amazon EC2 instance where you plan to deploy your IBM Db2 database and FSx for ONTAP must be in the same subnet.

  • Use separate storage virtual machines (SVM) for IBM Db2 data and log volumes. This ensures that your I/O traffic flows through different IP addresses and TCP sessions.

  • /db2/<DBSID>/sapdata1, /db2/<DBSID>/sapdata<x>, /db2/<DBSID>/log_dir, /db2/<DBSID>/saptmp<x>, /db2/<DBSID>/log_arch, and /usr/sap must have their own FSx for ONTAP volume.

  • FSx for ONTAP creates endpoints for accessing your file system in a Amazon VPC route table. FSx for ONTAP uses your Amazon VPC main route table. We recommend configuring your file system to use all of your Amazon VPC route tables that are associated with the subnets in which your clients are located. Alternatively, you can specify one or more route tables for Amazon FSx to use when you create your file system.

Supported instance types

Amazon FSx for NetApp ONTAP is supported for SAP applications using IBM Db2 database in a Single or Multi-Availability Zone deployment. You can use FSx for ONTAP as the primary storage solution for IBM Db2 database devices and backup volumes with supported Amazon EC2 instances. For a complete list of supported Amazon EC2 instances for IBM Db2, see SAP Note 1656099 - SAP Applications on Amazon EC2: Supported DB/OS and Amazon EC2 products (requires SAP portal access).

Sizing

Note

A single FSx for ONTAP file system can provide a maximum output of 80,000 IOPS. Select multiple FSx for ONTAP file systems if your IO requirement exceeds 80,000 IOPS. For more information, see Performance details.

You can configure the throughput capacity of FSx for ONTAP when you create a new file system by scaling up to 2 GB/s of read throughput and 750 MB/s of write throughput in a single Availability Zone deployment. For more information, see Performance details.