メインコンテンツへスキップ

Delete unused Oracle Cloud reserved public IPs

This tutorial uses a CloudFlow template to find unassigned regional reserved public IPs and request approval before deletion. Oracle Cloud nodes are available to customers enrolled in Early Access.

Goal and objectives​

  • Goal: Run a daily flow that finds unassigned reserved public IPs in a compartment and requests approval before deleting the candidate batch.

  • Objectives: In this tutorial, you'll learn how to:

    • Configure ListPublicIps for regional reserved addresses.

    • Review the preconfigured unassigned-address filter.

    • Configure an approval that expires within 24 hours.

    • Validate read-only nodes without testing the deletion.

注意

An unassigned address can still be reserved for DNS, firewall allowlists, failover, disaster recovery, or infrastructure as code. Deleting it permanently releases the address. Verify its owner and dependencies before approval.

Before you begin​

  1. Make sure your DoiT account has the CloudFlow Editor or CloudFlow Manager permission. See CloudFlow permissions.

  2. Make sure the tenancy exists as an OCI Asset and has the CloudFlow IAM policy.

  3. Create an Oracle Cloud connection.

  4. Identify the compartment and subscribed region that contain the reserved public IPs.

Create the flow from the template​

  1. Sign in to the DoiT console, select Automation and operations, and then select CloudFlow.

  2. Select Templates, then select Delete unused Oracle Cloud reserved public IPs.

  3. Open the Daily schedule trigger, select a future start date, and choose the time zone and daily run time.

Keep the flow as a draft while you validate its read-only nodes.

Configure and test inventory​

  1. Open the ListPublicIps node.

  2. On the Parameters tab, select the compartment and region. Keep Scope set to REGION and Lifetime set to RESERVED.

  3. On the Connection tab, select the Oracle Cloud connection.

  4. Test the node. Confirm that the results contain the expected reserved addresses, then select Save as test data.

Review the candidate filter​

The Filter deletion candidates node keeps public IPs whose assignedEntityId is empty.

Test the filter and review every candidate. An empty assignment does not prove that the address has no external dependency.

Configure approval and deletion​

  1. Open the DeletePublicIp node and select the same compartment, region, and connection.

  2. Keep Require approval for this action enabled.

  3. Enter the email or Slack recipient responsible for the network resources.

  4. Review the approval message and confirm that Reject approval after certain time is set to no more than 24 hours.

  5. Don't test the DeletePublicIp node unless you intend to release every address resolved from the upstream candidate list. Node tests perform the real operation without displaying the configured approval.

Immediately before an approved deletion, CloudFlow retrieves the address again, requires it to remain AVAILABLE, RESERVED, and unassigned, and sends the deletion with the current ETag.

Publish and monitor the flow​

Select Publish. The flow runs on its daily schedule and sends an approval request containing the deletion candidates. Approving the request authorizes deletion of all reserved public IPs listed in that request; CloudFlow revalidates each address before deletion.

Use Run history to inspect the inventory, filter, approval, and deletion results. Reject any request whose DNS, network, or recovery dependencies are unclear.

See also​

に最終更新