Task 10: (Optional) Clean Up Resources
After you've finished with the resources you created for this tutorial, you can delete and release the resources you no longer plan to use.
Perform the following tasks in the order listed:
After you detach a block volume, you can delete it as long as the volume isn't attached to any other instances.
You can't undo a termination. Any data on a volume is permanently deleted when the volume is deleted.
-
Click the Compute Cloud@Customer Console Dashboard, and click Compute/View Instances.
-
Select the Sandbox compartment.
-
Click the name of your instance.
-
In the Resources panel, click Attached Block Volumes.
-
Find your volume, click the Actions menu (
), then click Detach. Confirm the detachment.You might need to refresh the web page to see that the block volume is no longer attached.
-
Click Dashboard, and click Block Storage/View Block Volumes.
-
Select the Sandbox compartment.
-
Find your volume, click the Actions menu (
), and then click Terminate. Confirm the
termination.
Perform the next task:
You can permanently terminate (delete) instances that you no longer need. Any attached VNICs and boot volumes are automatically detached when the instance terminates. Eventually, the instance's public and private IP addresses are released and become available for other instances.
-
Click Dashboard, and click Compute/View Instances.
-
Select the Sandbox compartment.
-
Find the instance you created, click the Actions menu (
), then click
Terminate. -
In the Confirm Instances termination dialog box, move the
Permanently delete the attached boot volume
selector to the right, and click Confirm.Moving the selector to the right results in the boot volume being permanently deleted, which is appropriate for this tutorial.
In production, you can leave the selector in the left position to preserve the boot volume for use with another instance. This is convenient when you want to reuse a configured OS or data on the boot volume.
Perform the next task:
You can delete networking resources as long as the resource doesn't have any dependencies.
- Subnets: Must be empty (for example, no instance VNICs or route rules).
- VCNs: Must be empty and have no related resources or attached gateways (for example, no internet gateway, dynamic routing gateway, and so on).
-
Click Dashboard, and click Networking/View Virtual Cloud Networks.
-
Select the Sandbox compartment.
-
Click the name of your VCN.
-
Under Resources, click Route Tables.
-
Click the name of the route table.
-
For the route rule you created, click the Actions menu (
), click
Delete, and confirm the deletion.The route rule is deleted.
-
In the breadcrumb path at the top of the page, click the name of your VCN.
The VCN details page is displayed.
-
Under Resources, click Internet Gateways.
-
For the internet gateway that you created, click the Actions menu (
), then click
Delete, and confirm the deletion.The internet gateway is deleted.
-
Under Resources, click Subnets.
-
For the subnet you created, click the Actions menu (
), then click
Delete, and confirm the deletion.The subnet is deleted.
-
At the top of the VCN details page, click Terminate and confirm the termination.
The VCN is deleted.
Perform the next task:
You must remove all resources from a compartment before you can delete it, otherwise, the delete action fails and the compartment returns to an active state.
On Compute Cloud@Customer, IAM resources such as compartments are managed in Oracle Cloud Infrastructure (OCI), and synchronized to Compute Cloud@Customer.
-
Sign in to the Oracle Cloud Console in OCI using your federated identity credentials.
For more information, see Sign In to the Console.
-
In the Oracle Cloud Console navigation menu, click Identity & Security, then under Identity, click Compartments.
-
For the Sandbox compartment, click the Actions menu (
), and then click
Delete. -
Confirm the deletion.
This concludes the tutorial.