Configure external MinIO

Configure Splunk AppDynamics Virtual Appliance to use a self-managed MinIO service.

Use MinIO rather than a generic S3-compatible service. The installation uses MinIO administration capabilities to prepare the required buckets and access.

Storage Requirements

Ensure that you have sufficient storage on Kafka deployment to create required PVCs.
Profile Storage
Medium 500Gi
Extra Large 1500Gi
  1. Prepare a production-ready MinIO service.

    • Ensure that the MinIO RELEASE.2025-09-07T16-13-09Z is installed.

    • Provide a stable private DNS endpoint and S3 API port. The default MinIO S3 API port is 9000.
    • Allow OpenShift workloads to resolve and reach the endpoint.
    • Configure availability, capacity, monitoring, backups, restore, retention, and disaster recovery.
    • Enable TLS and use a server certificate whose SAN covers the configured host name.
  2. Choose how the installation manages MinIO users.
    Mode Credential supplied Behavior
    manageUsers: true Dedicated administrator credential The installation creates separate consumer users and policies, and prepares buckets and lifecycle rules.
    manageUsers: false Pre-provisioned, non-administrator S3 credential The installation uses one credential for all consumers and prepares buckets and lifecycle rules.

    Use manageUsers: false when policy does not permit the installation to create MinIO users. Ensure that the supplied identity can use the eum.appdynamics.* bucket prefix.

  3. Prepare the MinIO credential for the selected mode.
    • For manageUsers: true, use a dedicated temporary administrator identity that can create users and policies and perform S3 operations on the eum.appdynamics.* prefix.
    • For manageUsers: false, create one identity with object read, write, and delete access; bucket listing and location access; bucket creation; lifecycle configuration; versioning configuration; and bucket-policy management on the eum.appdynamics.* prefix.

    The non-administrator identity must permit the operations represented by s3:PutObject, s3:GetObject, s3:DeleteObject, s3:ListBucket, s3:GetBucketLocation, s3:CreateBucket, lifecycle configuration, bucket versioning, and bucket-policy management.

  4. Configure the MinIO endpoint in config/external-minio.yaml.
    CODE 
    statefulServices:
  minio:
    schemaVersion: 1
    external:
      host: "minio.storage.example.internal"
      port: 9000
      manageUsers: true

    Set manageUsers that matches the credential model you selected.

  5. Add the MinIO CA to the installation bundle.

    Save the complete PEM-encoded public CA chain as config/minio-ca.crt. The CA file is required for external MinIO, and the installation always verifies the server certificate.

  6. Add the MinIO credential to the protected config/secrets.yaml file.
    CODE 
    minio:
  external:
    accessKey: "<minio-access-key>"
    secretKey: "<minio-secret-key>"

    For administrator mode, provide the dedicated administrator credential. For pre-provisioned mode, provide the permanent runtime credential.

    Keep config/secrets.yaml out of source control and restrict access to it.

  7. Validate MinIO before installation.
    • Confirm connectivity from the OpenShift network.
    • Confirm TLS trust and that the endpoint host name matches a certificate SAN.
Install Virtual Appliance with external services after you configure every external service required by the target release.