Exadata Infrastructure
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 AI Database on Dedicated Infrastructure. Creating an Oracle Exadata Infrastructure may take up to 15 minutes or more.
- Complete the prerequisites before creating an Exadata Infrastructure. For more information, see Prerequisites.
- From the Oracle AI Database@AWS dashboard or the Exadata Infrastructure list, select the Create Exadata Infrastructure button.
- The Exadata Infrastructure creation process is a four (4) step process.
- In the Configure general settings step, do the following substeps.
- 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(-).
- 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.
- 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.

- In the Configure Exadata infrastructure step, do the following substeps.
- From the dropdown list, select the Exadata system model you want to use for this deployment. The Exadata system model list populates dynamically based on the selected Availability Zone. For example, if the selected Availability Zone supports Exadata.X9M, Exadata.X11M and Exadata.X11MV models, the list displays these options.
- If you select Exadata.X9M as the Exadata system model, use the slider to set values for Database servers and Storage servers. When the Exadata.X9M option is selected, the Database server type and Storage server type fields are disabled.

- If you select Exadata.X11M as the Exadata system model, the Database server type and Storage server type fields automatically populate with values. The Database server type field displays X11M, and the Storage server type field displays X11M-HC. Use the slider or enter the values for Database servers and Storage servers based on your system requirements.
- If you select Exadata.X11MV as the Exadata system model, the Database server type and Storage server type fields automatically populate with values. The Database server type field displays X11MV, and the Storage server type field displays X11MV-HC. Use the slider or enter the values for Database servers and Storage servers based on your system requirements.
Note
The X11MV infrastructure model for Oracle Exadata Database Service on Dedicated Infrastructure is available in the following AWS regions:AWS Region Physical Zone Asia Pacific (Hyderabad) aps2-az1Asia Pacific (Hyderabad) aps2-az3US Midwest (Columbus) us-columbus-1 - 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.

- In the Configure maintenance and tags step, do the following substeps.
- 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.
- 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.
- Select the check box to Enable timeout before performing maintenance on DB servers and specify a waiting period before server maintenance begins.
Note
The minimum value is 15 minutes and the maximum value is 120 minutes. - 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.
- 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.
- 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.

- 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.
- Once the Exadata Infrastructure is created, you can view the details of it from the Exadata Infrastructure list on the Oracle AI Database@AWS dashboard.

Exadata Infrastructure creation is only available through the AWS Console and AWS CLI.
There is currently no content for this page. Oracle AI Database@AWS team intends to add content here, and this placeholder text is provided until that text is added. The Oracle AI Database@AWS team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.
Exadata Infrastructure creation is only available through the AWS Console and AWS CLI.
You can provision an Exadata Infrastructure in AWS using the Terraform Provider hashicorp/aws (version 6.15.0 or higher).
Prerequisites- Terraform or OpenTofu installed
- AWS credentials configured
- HashiCorp AWS provider version >= 6.15.0
Sample Terraform ConfigurationFor detailed configuration options, see the following Terraform Provider documentation:# Create an Exadata Infrastructure resource "aws_odb_cloud_exadata_infrastructure" "this" { # Required Arguments display_name = "exadb-inf-demo" shape = "Exadata.X11M" compute_count = 2 storage_count = 3 availability_zone_id = "usw2-az3" # Optional Arguments customer_contacts_to_send_to_oci = [ { email = "demo@example.com" } ] region = "us-west-2" availability_zone = "us-west-2c" database_server_type = "X11M" storage_server_type = "X11M-HC" tags = { "env" = "dev" } maintenance_window { patching_mode = "ROLLING" preference = "NO_PREFERENCE" is_custom_action_timeout_enabled = false custom_action_timeout_in_mins = 15 days_of_week = null hours_of_day = null lead_time_in_weeks = null months = null weeks_of_month = null } } # Get list of DB Servers for provisioning VM Cluster / Autonomous VM Cluster data "aws_odb_db_servers" "this" { cloud_exadata_infrastructure_id = aws_odb_cloud_exadata_infrastructure.this.id } # Optional output of OCIDs for configurations using OCI Terraform Provider output "oci_region" { value = regex("(?i:region=)([^?&/]+)", aws_odb_cloud_exadata_infrastructure.this.oci_url)[0] } output "oci_compartment_ocid" { value = regex("(?i:compartmentId=)([^?&/]+)", aws_odb_cloud_exadata_infrastructure.this.oci_url)[0] } output "oci_tenant" { value = regex("(?i:tenant=)([^?&/]+)", aws_odb_cloud_exadata_infrastructure.this.oci_url)[0] } output "oci_cloud_exadata_infrastructure_ocid" { value = aws_odb_cloud_exadata_infrastructure.this.ocid }Reference Implementation
To review examples of integrated Terraform solutions, see the terraform-oci-multicloud-aws GitHub repository.
What's Next?
Oracle AI Database@AWS allows you to accept the offer and create an ODB network or Exadata Infrastructure in your Owner Account. You can share these resources with the Trusted Account within your organization using Resource Sharing.
In the Trusted Account, you can create Exadata VM Cluster, Autonomous VM Cluster, Exadata Database, Autonomous AI Database using Exadata Infrastructure created in Owner Account. If you want to use the Resource Sharing as the deployment model, complete the steps described in the Resource Sharing (Optional) documentation. If you do not want to use the Resource Sharing as the deployment model, then you can proceed to either create an Exadata VM Cluster or create an Autonomous VM Cluster.