sidebar | permalink | keywords | summary |
---|---|---|---|
sidebar |
task_managing_compliance.html |
remove, delete, stop, stop scans, stop scanning, cloud compliance, stop cloud compliance, delete cloud compliance, terminate, deactivate, deactivating cloud compliance |
If you need to, you can stop Cloud Compliance from scanning one or more working environments. You can also delete the Cloud Compliance instance if you no longer want to use Cloud Compliance with your Cloud Volumes ONTAP systems. |
If you need to, you can stop Cloud Compliance from scanning one or more working environments. You can also delete the Cloud Compliance instance if you no longer want to use Cloud Compliance with your Cloud Volumes ONTAP systems.
When you deactivate scans, Cloud Compliance no longer scans the data on the system and it removes the indexed compliance insights from the Cloud Compliance instance (the data from the working environment itself isn’t deleted).
You can delete the Cloud Compliance instance if you no longer want to use Cloud Compliance with Cloud Volumes ONTAP. Deleting the instance also deletes the associated disks where the indexed data resides.
-
Go to your cloud provider’s console and delete the Cloud Compliance instance.
The instance is named CloudCompliance with a generated hash (UUID) concatenated to it. For example: CloudCompliance-16bb6564-38ad-4080-9a92-36f5fd2f71c7