Creating an Oracle Exadata Infrastructure is a prerequisite for provisioning Oracle Exadata VM Clusters , Oracle Autonomous VM Cluster and any Oracle Exadata Databases, including Oracle Autonomous Database on Dedicated Infrastructure. Creating an Oracle Exadata Infrastructure is a time-consuming process and it may take up to 15 minutes.

1. Complete the prerequisites before creating an Exadata Infrastructure. For more information, see Prerequisites.
2. From the Oracle Database@AWS dashboard or the Exadata Infrastructure list, select the Create Exadata Infrastructure button.
3. The Exadata Infrastructure creation process is a four (4) step process.
4. In the Configure general settings step, do the following substeps.
   1. In the Exadata infrastructure name field, enter an identifier of your choice for the name. The identifier can be up to 255 characters. It can include the following characters: a-z, A-Z, 0-9, underscore (_), and dash (-). It must start with a letter or underscore (_) and cannot contain two successive hyphens(-).
   2. The Availability Zone field is a drop-down that contains the AZ where the Exadata Infrastructure will exist. The list is limited by your subscription.
   3. Select the Next button to continue the creation process, or the Cancel button to stop the creation process and return to the Exadata Infrastructure list.
5. In the Configure Exadata infrastructure step, do the following substeps.
   1. The Exadata system model is a drop-down field that allows you to select system model.
      The Exadata system model dropdown list populates dynamically based on the selected Availability Zone. For example, if the selected Availability Zone supports both Exadata.X9M and Exadata.X11M models, these two options will be displayed in the dropdown list.
   2. If you select Exadata.X9M as the Exadata system model, the Database servers field, use the slider or enter a value from 2 to 32 and builds to OCPUs. The Storage servers field, use the slider or enter a value from 3 to 64. The Database server type and Storage server type fields are disabled when the Exadata.X9M Exadata system model is selected.
   3. If you select Exadata.X11M as the Exadata system model, the Database server type and Storage server type fields are enabled, but there is currently only a single choice for each field. The Database servers field, use the slider or enter a value from 2 to 32 and builds to ECPUs. The Storage servers field, use the slider or enter a value from 3 to 64.
   4. Select the Next button to continue the creation process, or the Cancel button to stop the creation process and return to the Exadata Infrastructure list.
6. In the Configure maintenance and tags step, do the following substeps.
   1. The Window type provides two options for managing your maintenance. These two options are Oracle-managed schedule and Customer-managed. If you select the Oracle-managed schedule option, the system automatically assigns a date and start time for Exadata Infrastructure maintenance. If you select the Oracle-managed schedule option, you must set a date and start time for your Exadata Infrastructure maintenance.
   2. The Patching mode type provides two options including Non rolling and Rolling. By default, the Non rolling option is selected. Make a selection based on your patching preferences.
   3. Select the check box to Enable timeout before performing maintenance on DB servers and specify a waiting period before server maintenance begins.
      The minimum value is 15 minutes and the maximum value is 120 minutes.
   4. In the OCI maintenance notification contacts field, you can enter up to 10 email addresses for notification about maintenance updates. AWS forwards the addresses to Oracle, who emails the notifications.
   5. You can enter Tags, if desired or required, by selecting the Add new tag button. Do this for each tag you want or need to add.
   6. Select the Next button to continue the creation process, or the Cancel button to stop the creation process and return to the Exadata Infrastructure list.
7. In the Review and create step, actively review the settings you have selected. Return to previous steps if any changes are needed. When finished, select the Create Exadata infrastructure button, or the Cancel button to cancel Exadata Infrastructure creation. Either way, you will return to the Exadata Infrastructure list. You can monitor the status of your Exadata Infrastructure creation request, or manage existing Exadata Infrastructures.
8. Once the Exadata Infrastructure is created, you can view the details of it from the Exadata Infrastructure list on the Oracle Database@AWS dashboard.