Re-Enabling Cloud Guard

You can re-enable Cloud Guard after disabling it.

Note

When you re-enable Cloud Guard, none of the targets, user-managed detector and responder recipes, and other customizations that Cloud Guard had before it was disabled are restored. You must manually re-create this infrastructure after re-enabling Cloud Guard.
    1. Verify that Cloud Guard prerequisites are still in place.
    2. Perform the same steps used to enable Cloud Guard for the first time.
      See Enabling Cloud Guard.

      If you want to get Cloud Guard up and running as quickly as possible, before you re-create previous customizations, follow the "fast track" option.

      Note

      If you re-enable Cloud Guard in a different reporting region, it takes up to an extra 15 minutes for the enablement process to complete.

      The Cloud Guard reporting region is not the same thing as the OCI home region.

  • For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

    Use the oci cloud-guard configuration update command and required parameters to update the details of the configuration for a Cloud Guard tenancy, to re-enable Cloud Guard:

    oci cloud-guard configuration update --compartment-id, -c <compartment_ocid> --reporting-region reporting_region_value --status tenancy_enablement_status [OPTIONS]
  • Run the UpdateConfiguration operation to update the details of the configuration for a Cloud Guard tenancy, to re-able Cloud Guard.