Locking an Outbound Connector
Lock a File Storage outbound connector to prevent updates, moves, and deletions. Locks help protect resources against tampering.
A lock on an outbound connector resource doesn't prevent the outbound connector from being used by a mount target to communicate with the external server.
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 outbound connector, you need permissions to manage locks.
To lock an outbound connector, you must have RESOURCE_LOCK_ADD permissions.
- Open the navigation menu and select Storage. Select File Storage.
- Under Additional resources, click Outbound Connectors.
- In the List scope section, under Compartment, select a compartment.
- In the list of outbound connectors, click the name of the outbound connector that you want to lock.
- On the outbound connector's details page, next to Resource Locking, select Add.
- In the Add Lock window, select the lock type and click Save changes.
Use the
oci fs outbound-connector addcommand and required parameters to lock an outbound connector:oci fs outbound-connector add --outbound-connector-id <outbound_connector_id> --type <lock_type>For a complete list of parameters and values for CLI commands, see the CLI Command Reference.
Run the AddOutboundConnectorLock operation to lock an outbound connector.
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.