Oracle Cloud Infrastructure Documentation

Locking a Mount Target

Lock a File Storage mount target to prevent updates, moves, and deletions of the resource. Locks help protect resources against tampering.

Important

A lock on a mount target resource doesn't prevent authorized users from mounting and accessing a file system, or changing the contents of the mounted file system.

OCI resource locks include the following types:

  • Delete lock: Prevents deletion of the locked resource.
  • Full lock: Prevents update, move, and deletion of the locked resource.

You can only add or remove one lock type at a time, but both locks can be applied to a resource. For example, you might initially apply a delete lock, but choose to apply a full lock at a later time.

The user who places a lock is the lock owner. Any authorized user with lock privilege or users with global manage permission of the tenancy has the authorization to create and remove any lock in the tenancy. You can override or remove locks.

Required IAM Policy

To create locks, in addition to permissions to manage the mount target, you need permissions to manage locks.

To lock a mount target, you must have RESOURCE_LOCK_ADD permissions.

    1. Open the navigation menu and click Storage. Under File Storage, click Mount Targets.

    2. In the List scope section, under Compartment, select a compartment.

    3. In the list of mount targets, click the name of the mount target that you want to lock.
    4. On the mount target's details page, next to Resource Locking, select Add.
    5. In the Add Lock window, select the lock type and click Save changes.

  • Use the oci fs mount-target add command and required parameters to lock a mount target:

    oci fs mount-target add --mount-target-id <mount_target_OCID> --type <lock_type>

    For a complete list of parameters and values for CLI commands, see the CLI Command Reference.

  • Run the AddMountTargetLock operation to lock a mount target.

    For information about using the API and signing requests, see REST API documentation and Security Credentials. For information about SDKs, see SDKs and the CLI.