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

1. From the Oracle Database@AWS dashboard, select the Autonomous VM Clusters link, and then select the Create Autonomous VM cluster button to start the provisioning flow.
2. The Autonomous VM Cluster creation process is a five (5) step process.
3. In the Configure general settings step, do the following substeps.
   1. In the Autonomous 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, underscores (_), and hyphens (-). It must start with a letter or underscore (_) and cannot contain two successive hyphens(-).
   2. The Description field is optional. You can enter a description using up to 400 characters.
   3. The Time zone drop-down allows you to select the time zone for your Autonomous 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 Autonomous VM Clusters 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 for your Autonomous VM Cluster. 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 Database servers section allows you to designate the servers. At a minimum, you must select two Database servers.
   3. The Configuration: ECPU count per VM slider allows you to set the ECPU count. The minimum and maximum values depend upon your Exadata Infrastructure available capacity and Autonomous VM Cluster settings.
   4. The Configuration: Database memory per ECPU slider allows you to set the memory per ECPU allocated for the Autonomous Database in the Autonomous VM Cluster. The minimum and maximum values depend upon your Exadata Infrastructure and Autonomous VM Cluster settings.
   5. The Configuration: Database storage slider allows you to set the allocated data storage. The minimum and maximum values depend upon your Exadata Infrastructure and Autonomous VM Cluster settings.
   6. The Configuration: Maximum number of Autonomous Container Databases slider allows you to set the upper limit on Autonomous Container Databases(ACDs). The minimum and maximum values depend upon your Exadata Infrastructure available capacity, particularly the available capacity of the local storage on the Database servers.
   7. Select the Next button to continue the creation process, or the Cancel button to stop the process.
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 Scan listener port settings has the Port (non-TLS) and Port (TLS) fields. These fields are optional. The default for Port (non-TLS) is set to 1521 and the default for Port (TLS) is set to 2484. You can change the port setting to an available port within the range of 1024 to 8999, with exceptions for ports 1522, 1525, 5000, 6100, 6200, 7060, 7070, 7879, 808, 8181, 8888 and 8895.
   3. To Enable mutual TLS (mTLS) authentication, click the checkbox.
   4. Select the Next button to continue the creation process, or the Cancel button to stop the creation process.
6. In the Configure maintenance and tags step, do the following substeps.
   1. Under the Maintenance configuration section, the Window type has two options. 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 Autonomous VM cluster maintenance. If you select the Customer-managed option, you must choose a date and start time for Autonomous VM cluster maintenance.
   2. 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.
   3. Select the Next button to continue the creation process, or the Cancel button to stop the creation process.
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 Autonomous VM Cluster button, or the Cancel button to stop the creation process. Either way, you will return to the Autonomous VM Cluster list. You can monitor the status of your Autonomous VM Cluster creation request, or manage existing Autonomous VM Clusters. This step can take several hours.