Sizing - SAP BusinessObjects 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).

Sizing

At a high level, BOBI platform sizing is a two-step process. The first step is to get SAPS through the SAP Sizing tool Quick Sizer. The second step is to map the output to appropriate Amazon EC2 instance types. See the SAP BOBI sizing guide available from the SAP BusinessObjects Business Intelligence Platform help documentation. Follow the standard SAP Quick Sizer to determine the right SAPS requirements for your workload. Once you have identified the SAPS numbers, you can use any of the Amazon SAP certified instances for your SAP BOBI Platform instances. Make sure to read the SAP BusinessObjects Business Intelligence section of the note carefully to ensure that you meet the version, EC2 resource, operating system, and database requirements for Amazon.

For sizing your storage requirements for the database and app tier, Amazon provides various volume types, such as general purpose SSDs (gp3) and provisioned IOPS SSD (io2). You can read more about the differences at Amazon EBS Volume Types. As general guidance, we recommend that you consider the gp3 volume type as a starting point to see if it satisfies your throughput and IOPS requirement of your workload, and consider io2 volume types if you have a need for sustained IOPS.

It is easy to add capacity to your existing SAP BOBI deployment in Amazon. Therefore, for migrating your existing deployment to Amazon, you may not need the same degree of over-provisioning as is typical for on-premises environments.