Oracle Cloud - Start or Stop Compute Instances

Oracle Cloud - Start or Stop Compute Instances starts an Oracle Cloud instance for:

• Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

When accessing an enforcement action using the API, you must use the backend form of field names.

Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

📘

Note

• Not all asset types are supported for all Enforcement Actions.
• See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
• See Actions supported for Aggregated Security Findings.
• See Actions supported for Software.

Required Fields

These fields must be configured to run the Enforcement Set.

• Use stored credentials from Oracle Cloud adapter - Enable this to use credentials from the adapter connection. By default, the first connection is selected.

  • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

• Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

  
  

Additional Fields

These fields are optional.

• Choose action for compute instance
  • START - Starts the Oracle Cloud instance.
  • STOP - Stops the Oracle Cloud instance.

APIs

Axonius uses the following APIs:

• Public Cloud Machine REST API Reference for Oracle Compute Cloud Service
• ComputeClient — oci 2.125.0 documentation
• Stopping, Starting, or Restarting an Instance

Required Permissions

The stored credentials in the selected adapter connection must have permission to start or to stop the following Oracle Cloud instances:

• compute.instances.read
• compute.instances.update
• compute.instanceConsoleConnections.use
• compute.instanceAction