Provisioning an Oracle Exadata VM Cluster requires the existence of an Oracle Exadata Infrastructure, and an ODB Network, and is a prerequisite for Oracle Exadata Databases that runs on the cluster.

1. From the Oracle Database@AWS dashboard or the Exadata VM Cluster list, select the Create VM cluster button.
2. The Exadata VM Cluster creation process is a five (5) step process.
3. In the Configure general settings step, do the following substeps.
   1. In the VM cluster 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 hyphens (-). It must start with a letter or underscore (_) and cannot contain two successive hyphens(-).
   2. In the Grid infrastructure cluster name field, enter an identifier of your choice for the name. The identifier can be up to 11 characters. It can include the following characters: a-z, A-Z, 0-9, underscore (_), and hyphens (-). It must start with a letter or underscore (_) and cannot contain two successive hyphens(-).
   3. The Time zone drop-down allows you to select the time zone for your Exadata VM Cluster. UTC is the default option.
   4. The License options drop-down allows you to select either Bring Your Own License (BYOL) or License included. Bring Your Own License (BYOL) is the default option.
   5. 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.
4. In the Configure infrastructure settings step, do the following substeps.
   1. The Exadata infrastructure name drop-down allows you to select an existing Exadata Infrastructure. If one does not exist or you do not want to use an existing Exadata Infrastructure, you must Task 3: Create an Exadata Infrastructure for Oracle Database@AWS first.
   2. The Grid infrastructure version drop-down allows you to select from the supported versions for your selected Exadata Infrastructure.
   3. The Exadata image version drop-down allows you to select a specific version. Default is the default option, and it is the highest version available.
   4. The Database servers section allows you to designate the servers. At a minimum, you must select one Database servers.
   5. The Configuration: Per VM: OCPU core count slider allows you to set the OCPU core count. The minimum and maximum values depend upon your Exadata Infrastructure and Exadata VM Cluster settings.
   6. The Configuration: Per VM: Memory slider allows you to set the available memory. The minimum and maximum values depend upon your Exadata Infrastructure and Exadata VM Cluster settings.
   7. The Configuration: Per VM: Local storage slider allows you to set the available local storage. The minimum and maximum values depend upon your Exadata Infrastructure and Exadata VM Cluster settings.
   8. The Configuration: Per Cluster: Exadata Storage slider allows you to set the Exadata storage. The minimum and maximum values depend upon your Exadata Infrastructure settings.
   9. The Sparse disk group and Local backup checkboxes allow you to select these options at creation time. These specific options cannot be modified after creation.
   10. 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 connectivity step, do the following substeps.
   1. The ODB network drop-down allows you to select an existing ODB network. If one does not exist or you do not want to use an existing ODB network, you must Task 2: Create an ODB Network for Oracle Database@AWS first.
   2. The Host name prefix field allows you to enter a unique host name for the Exadata VM Cluster.
   3. The Host domain name and Host and domain name URL are read-only fields provided for reference and accuracy checks.
   4. The SCAN listener port (TCP/IP) field is optional, and is set to 1521 by default. You can change the port setting to an available port within the range of 1024 to 8999, with exceptions for ports 2484, 6100, 6200, 7060, 7070, 7085, and 7879.
   5. The SSH key pairs allows you to enter one or more SSH key pairs. Each entry must added individually.
   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.
6. In the Configure diagnostics and tags step, do the following substeps.
   1. The Diagnostic event checkbox allows Oracle to collection and send fault notifications for critical, warning, and information events. These will be sent to the OCI maintenance notification contacts for the Exadata Infrastructure.
   2. The Health monitor checkbox allows Oracle to collect health metrics like Oracle Database up/down, disk space usage, and others. These will be sent to the OCI maintenance notification contacts for the Exadata Infrastructure.
   3. 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. These will be sent to the contacts for the Exadata Infrastructure.
   4. The Incident logs and trace collections checkbox allows Oracle to collect incident logs and traces to enable fault diagnostics and issue resolution.
   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 VM cluster button, or the Cancel button to cancel Exadata Infrastructure creation. Either way, you will return to the Exadata VM Cluster list. You can monitor the status of your Exadata VM Cluster creation request, or manage existing Exadata VM Clusters. This step can take several hours.