AWS odb documentation change
Summary
Added documentation for deleting ODB peering connections and updated VM cluster deletion procedures. Added note about Zero-ETL integration being unsupported in preview.
Security assessment
Changes focus on operational procedures (deletion workflows) and feature availability notes. No evidence of addressing security vulnerabilities or describing security controls.
Diff
diff --git a/odb/latest/UserGuide/managing.md b/odb/latest/UserGuide/managing.md index 5939bfbfb..74fcd1b9a 100644 --- a//odb/latest/UserGuide/managing.md +++ b//odb/latest/UserGuide/managing.md @@ -5 +5 @@ -Updating an ODB networkDeleting an ODB networkDeleting a VM clusterDeleting an Exadata infrastructure +Updating an ODB networkDeleting an ODB networkDeleting a VM clusterDeleting an Exadata infrastructureDeleting an ODB peering connection @@ -46 +46,5 @@ This section assumes that you have already created an ODB network in [Step 1: Cr - 7. (Optional) For **VPC ID** , specify the ID of a VPC to use for ODB peering. + 7. (Optional) For **Configure service integrations** , select or deselect **Amazon S3** or **Zero-ETL**. + +###### Note + +In this preview, the **Zero-ETL** option appears in the console, but the Zero-ETL integration isn't supported. @@ -76 +80 @@ You can delete an ODB network. This section assumes that you have already create -## Deleting an Exadata VM cluster in Oracle Database@AWS +## Deleting a VM cluster in Oracle Database@AWS @@ -78 +82 @@ You can delete an ODB network. This section assumes that you have already create -You can delete an Exadata VM cluster. This section assumes that you have already created an Exadata VM cluster in [Step 3: Create an Exadata VM cluster or Autonomous VM cluster in Oracle Database@AWS](./getting-started.html#getting-started-vm). +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.html#getting-started-vm). @@ -80 +84 @@ You can delete an Exadata VM cluster. This section assumes that you have already -###### To delete an Exadata VM cluster +###### To delete an VM cluster @@ -84 +88 @@ You can delete an Exadata VM cluster. This section assumes that you have already - 2. From the left pane, choose **Exadata VM clusters**. + 2. From the left pane, choose **Exadata VM clusters** or **Autonomous VM clusters**. @@ -86 +90 @@ You can delete an Exadata VM cluster. This section assumes that you have already - 3. Choose an Exadata VM cluster to delete. + 3. Choose a VM cluster to delete. @@ -113,0 +118,23 @@ You can delete an Oracle Exadata infrastructure. This section assumes that you h +## Deleting an ODB peering connection + +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. + + 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/). + + 2. In the navigation pane, choose **ODB peering connections**. + + 3. Select the ODB peering connection to delete. + + 4. Choose **Delete**. + + 5. To confirm deletion, enter `delete me` and choose **Delete**. + + + + +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 + @@ -120 +147 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Configuring the network +Working with shared resources in a trusted account