Configure MinIO
Perform the following steps to configure MinIO:
Tip
Only the ACCESS_KEY authentication method is supported when connecting to MinIO, on every deployment type.
Note
Make sure to update the placeholders such as <AWS_ACCESS_KEY>, <AWS_SECRET_KEY>, <PROFILE_NAME>, <MINIO_HOST>, and <MINIO_PORT> with your actual configuration details.
- SSH to the instance where Privacera Manager is installed.
- Run the following command to open the
.ymlfile to be edited.Bash - Add the following properties to configure MinIO:
- Once the properties are configured, refer to the Privacera Manager Quickstart.
- In PrivaceraCloud, navigate to Settings → Applications.
- On the Connected Applications screen, select S3.
- Click the edit icon, then click Access Management.
-
Under the BASIC tab:
- Disable Use IAM Role.
- Provide values for the following fields:
- AWS Access Key:
<AWS_ACCESS_KEY> - AWS Secret Key:
<AWS_SECRET_KEY>
- AWS Access Key:
-
Under the ADVANCED tab, add the following custom properties with the appropriate value for
<PROFILE_NAME>,<MINIO_HOST>, and<MINIO_PORT>: - Click Test Connection to verify the connection.
- Once the connection is successful, click Save.
- Open the DataServer connector and go to Access Control Configs → Connector Configs.
- Choose the profile to use for MinIO:
- In the left panel, select a profile under Common Properties, or select Add Profile to create one.
- Set its Auth Method to Access Key.
- Enter the Access Key ID and the Secret Access Key.
- Expand the profile's S3-Compatible Endpoint (MinIO) section:
- Enable Custom S3 Endpoint.
- Set Custom S3 Endpoint Host (for example,
minio.example.com). - Set Custom S3 Endpoint Port (for example,
443). - Turn Custom S3 Endpoint SSL on to use TLS (default) or off for plain HTTP.
- Select Save. The Runtime Manager redeploys the connector.
- Prev topic: Advanced Configuration