# Managing Oracle Database@AWS
<a name="managing"></a>

You can modify and delete some Oracle Database@AWS resources after you create them.

## Updating an ODB network in Oracle Database@AWS
<a name="managing.updating"></a>

You can update the following ODB network resources:
+ The ODB network name
+ The Amazon VPC to use for establishing an ODB peering connection to the ODB network
+ The VPC CIDR ranges that can access Exadata resources in the ODB network
**Note**  
By specifying CIDR ranges, you limit connectivity to the necessary VPC subnets instead of making the entire VPC available to the ODB network.

This section assumes that you have already created an ODB network in [Step 1: Create an ODB network in Oracle Database@AWS](getting-started.md#getting-started-odb).

**To update an ODB network**

1. Sign in to the AWS Management Console and open the Oracle Database@AWS console at [https://console.aws.amazon.com/odb/](https://console.aws.amazon.com/odb/).

1. From the left pane, choose **ODB networks**.

1. Select the network that you want to modify.

1. Choose **Modify**.

1. (Optional) For **ODB network name**, enter a new network name. The name must be 1–255 characters and begin with an alphabetic character or underscore. It can't contain consecutive hyphens.

1. (Optional) For **Peered CIDRs**, specify CIDR ranges from the peered VPC that need connectivity to the ODB network. To limit access, we recommend that you specify the minimum required CIDR ranges.

1. (Optional) For **Configure service integrations**, select or deselect **Amazon S3** or **Zero-ETL**.

1. Choose **Continue**, and then choose **Modify**.

## Deleting an ODB network in Oracle Database@AWS
<a name="managing.deleting-network"></a>

You can delete an ODB network. This section assumes that you have already created an ODB network in [Step 1: Create an ODB network in Oracle Database@AWS](getting-started.md#getting-started-odb). You can't delete an ODB network that is currently in use by a VM cluster.

**To delete an ODB network**

1. Sign in to the AWS Management Console and open the Oracle Database@AWS console at [https://console.aws.amazon.com/odb/](https://console.aws.amazon.com/odb/).

1. From the left pane, choose **ODB networks**.

1. Select the network that you want to delete.

1. Choose **Delete**.

1. (Optional) Choose **Delete associated OCI resources** to delete the OCI resources that were created along with the ODB network.

1. In the text box, enter **delete me**.

1. Choose **Delete**.

## Deleting a VM cluster in Oracle Database@AWS
<a name="deleting_vm_cluster"></a>

You can delete an Exadata VM cluster or Autonomous VM cluster. This section assumes that you have already created a VM cluster in [Step 3: Create an Exadata VM cluster or Autonomous VM cluster in Oracle Database@AWS](getting-started.md#getting-started-vm).

**To delete an VM cluster**

1. Sign in to the AWS Management Console and open the Oracle Database@AWS console at [https://console.aws.amazon.com/odb/](https://console.aws.amazon.com/odb/).

1. From the left pane, choose **Exadata VM clusters** or **Autonomous VM clusters**.

1. Choose a VM cluster to delete.

1. Choose **Delete**.

1. When prompted, enter **delete me** and then choose **Delete**.

## Deleting an Oracle Exadata infrastructure in Oracle Database@AWS
<a name="deleting_infra"></a>

You can delete an Oracle Exadata infrastructure. This section assumes that you have already created an Oracle Exadata infrastructure in [Step 2: Create an Oracle Exadata infrastructure in Oracle Database@AWS](getting-started.md#getting-started-infra). You can't delete an Exadata infrastructure that is currently in use by a VM cluster.

**To delete an Oracle Exadata infrastructure**

1. Sign in to the AWS Management Console and open the Oracle Database@AWS console at [https://console.aws.amazon.com/odb/](https://console.aws.amazon.com/odb/).

1. From the left pane, choose **Exadata infrastructures**.

1. Choose an Exadata infrastructure to delete.

1. Choose **Delete**.

1. When prompted, enter **delete me** and then choose **Delete**.

## Deleting an ODB peering connection
<a name="network-peering-delete"></a>

When you no longer need an ODB peering connection, you can delete it. You must delete all ODB peering connections before you can delete an ODB network.

### Console
<a name="DeletePeering.CON"></a>

1. Sign in to the AWS Management Console and open the Oracle Database@AWS console at [https://console.aws.amazon.com/odb/](https://console.aws.amazon.com/odb/).

1. In the navigation pane, choose **ODB peering connections**.

1. Select the ODB peering connection to delete.

1. Choose **Delete**.

1. To confirm deletion, enter **delete me** and choose **Delete**.

### AWS CLI
<a name="DeletePeering.CLI"></a>

To delete an ODB peering connection, use the `delete-odb-peering-connection` command.

```
aws odb delete-odb-peering-connection \
    --odb-peering-connection-id odbpcx-1234567890abcdef
```