# Prerequisites
<a name="prereq-orc-sap-nw-lx"></a>

We recommend familiarizing yourself with these guides:
+  [SAP on Amazon Overview and Planning](https://docs.amazonaws.cn/sap/latest/general/sap-on-aws-overview.html) 
+  [Getting Started with Architecting SAP on the Amazon Cloud](https://www.amazonaws.cn/blogs/awsforsap/getting-started-with-architecting-sap-on-the-aws-cloud/) 
+  [Best practices for Amazon EC2](https://docs.amazonaws.cn/AWSEC2/latest/UserGuide/ec2-best-practices.html) 
+  [Migrating Oracle Database Workloads to Oracle Linux on Amazon](https://d1.awsstatic.com/whitepapers/migrating-oracle-database-workloads-to-oracle-linux-on-aws.pdf) 
+  [Determining the IOPS Needs for Oracle Database on Amazon](https://docs.amazonaws.cn/whitepapers/latest/determining-iops-needs-oracle-db-on-aws/determining-iops-needs-oracle-db-on-aws.html) 
+  [SAP Note 2606828 - Oracle Database Roadmap for SAP NetWeaver](https://me.sap.com/notes/2606828) (SAP portal access required)

## Technical requirements
<a name="w283aac21c11c15"></a>

Before you begin deploying Oracle database for SAP applications on Amazon, ensure that you meet the following requirements:
+ If necessary, request a service limit increase by creating a support ticket. This is to ensure that the Amazon services required for Oracle database deployment are not constrained by the default limit. For more information, see [Amazon service quotas](https://docs.amazonaws.cn/general/latest/gr/aws_service_limits.html). For example, you may have to increase the Amazon EC2 instance limit before your Oracle deployment.
+ You will need the following information for your existing resources while running the Amazon CLI commands to create Amazon EC2 and Amazon Elastic Block Store [(Amazon EBS)](https://www.amazonaws.cn/ebs/) resources.


**Information**  

|  |  | 
| --- |--- |
|  **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. | 
| 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. You can find the latest Linux AMIs on [Amazon Marketplace](https://www.amazonaws.cn/marketplace). | 
| 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. | 
| Access key ID | Access key for your Amazon account that will be used with Amazon CLI tools. | 
| Secret access key | Secret key for your Amazon account that will be used with Amazon CLI tools. | 
+ Create security groups and open ports to enable communication. For existing security groups, ensure that the required ports are open. For a list of ports, refer to [TCP/IP ports of all SAP products](https://help.sap.com/viewer/ports) and [Managing Oracle Database Port Numbers](https://docs.oracle.com/database/121/SSDBI/app_port.htm#SSDBI7924).
+ Ensure that you have installed and configured Amazon CLI with required credentials, if you plan to use it to launch instances. For more information, see [Installing the Amazon CLI](https://docs.amazonaws.cn/cli/latest/userguide/cli-chap-install.html).
+ If you plan to use the Amazon Management Console, ensure that you have the essential credentials and permissions to launch and configure Amazon services. For more information, see [Access management for Amazon resources](https://docs.amazonaws.cn/IAM/latest/UserGuide/access.html).
+ Ensure that you have the software files required for installation readily available. You can stage these in [Amazon S3](https://www.amazonaws.cn/s3/) or [Amazon Elastic File System](https://www.amazonaws.cn/efs/) (Amazon EFS). Amazon EFS can be easily shared on all of your installation hosts. For more information, see [Create your Amazon EFS file system](https://docs.amazonaws.cn/efs/latest/ug/gs-step-two-create-efs-resources.html).
+ Oracle for SAP on Amazon is supported on an OEL OS. For more information, see [SAP Note 1656099](https://me.sap.com/notes/1656099) and [SAP Note 2358420](https://me.sap.com/notes/2358420) (login required). If you are currently using a different OS, you can procure licenses and perform a migration. For more information, see [Migrating Oracle Database Workloads](https://d1.awsstatic.com/whitepapers/migrating-oracle-database-workloads-to-oracle-linux-on-aws.pdf). To use AMIs published by Oracle, see [Launch an Oracle Linux instance in Amazon](https://community.oracle.com/tech/apps-infra/discussion/4417739/launch-an-oracle-linux-instance-in-aws).