This page provides a guide to configuring S3 Compatible storage as a Storage Target in Verba. Verint does not certify S3 compatible storage platforms unless it is specified otherwise. Customers successfully deployed Verba with the following storage platforms using the S3 Compatible storage target:
Verba supports both the V2 (REST) and V4 authentication types.
WORM features are also supported in the case of IBM COS storage, which allows putting retention or Legal Hold on the objects created by Verba. For more information, see WORM.
For a general description of storage targets, please refer to Storage and export targets.
Creating an S3 Compatible storage target
Follow the steps below to create a new Verba Storage target for S3 Compatible storage target:
Step 1 - Open the Verba Web interface then select Data / Storage Targets from the top menu.
Step 2 - Click on Add New Storage Target
Step 3 - Fill out the configuration form according to the requirements in the following table.
|Name||Name your storage target. This name will identify this target across the system.|
|Type||Select S3 Compatible Storage|
The name of your bucket
Bucket names must contain only lowercase letters, numbers, periods (.) and dashes (-).
Do not specify folders or subfolders, the system does NOT support subfolders, only the root folder of the bucket is supported.
Specify the S3 compatible API endpoint. It can be found in the documentation of the storage platform.
Do not specify folders or subfolders, the system does NOT support subfolders.
|Enable Object Lock and Legal Hold|
Select the checkbox if the object lock feature will be used for retention and legal hold. This is supported only in the case of IBM COS storage.
Specifies the addressing mode used for connecting to the bucket.
Virtual Hosted Style: Changes the HTTP HOST header to include the bucket name.
For example https://bucketname.rest-endpoint.com/key-name
Path Style: Sets the bucket in the URL.
For example https://rest-endpoint.com/bucket-name/key-name
Select either "AWS Signature Version 2" or "AWS Signature Version 4" according to the supported authentication type of the storage target being used.
In the case of IBM COS storage, select "AWS Signature Version 4 IBM".
|Access Key Id||Access Key Id of the S3 compatible storage|
|Secret Access Key||Secret Access Key of the S3 compatible storage|
|Region||The region of the bucket. Only required if V4 authentication is being used. In the case of on-prem storage, it can be anything.|
Step 4 - Click Save to save the settings
Forward proxy configuration
In order to configure a forward proxy for the S3 Compatible storage connections, follow the steps below:
In the Verba menu, navigate to System / Verba Servers, select the appropriate server, then click on the Change Configuration tab.
On this tab, fill in the configuration under Storage Management / Storage Targets / S3 Compatible. See the table below for reference.
|Forward Proxy Address|
IP address or FQDN of the forward proxy. When defined, the system will connect through a forward proxy.
|Forward Proxy Port||The port of the forward proxy|
|Forward Proxy Username||Username for basic authentication for the forward proxy server|
|Forward Proxy Password||Password for basic authentication for the forward proxy server|
TLS connection configuration
By default, Verba uses the server certificate for the TLS connection. Its details can be found under the Server Certificate node in the server configuration.
When needed, a custom certificate can be used instead, and other connection properties can be also changed.
In the Verba menu, navigate to System / Servers, select the appropriate server, then click on the Change Configuration tab.
On this tab, fill out the configuration under Storage Management / Storage Targets / S3 Compatible. See the table below for reference.
|Use Https Protocol||Set to yes, if a secure connection should be used|
|Connection Timeout (ms)||Defines the connection timeout value in milliseconds.|
|TLS Key password|
Specify the password for the file that contains the certificate keys
|TLS Key file|
Specify the file where the certificate key is stored
|TLS Certificate||Path to the certificate|
|TLS CA Certificate||Path to the CA certificate|