Hello Vapi, We are trying to configure custom S3 storage for a HIPAA compliant workflow with Vapi. We’ve already enabled HIPAA compliance and understand that Vapi can push call recordings and transcripts to a self-hosted S3-compatible endpoint. However, it’s unclear how to provide a custom endpoint URL for Vapi to push recordings to our storage server. Right now, we are using MinIO for S3 compatible storage, but we need to know how to get Vapi to point to this rather than using AWS S3. For context, our MinIO server is hosted on our own server, is reachable via HTTPS (we’ve whitelisted storage.vapi.ai), and configured with access and secret keys that mimic AWS S3 authentication. This is what support has told us to use: { "provider": "s3", "name": "Internal MinIO Storage", "awsAccessKeyId": "", "awsSecretAccessKey": "", "region": "us-east-1", "s3BucketName": "recordings", "s3PathPrefix": "vapi/", "endpointUrl": https://portal.myhealthcarestartup.com:9800/ } and were told to post the request to https://api.vapi.ai/credential but the API tells us endpointUrl is not a valid parameter. What is the exact parameter name and format used to specify the URL of a self-hosted MinIO server in the storage configuration? Thank you!

Thank you for the detailed context. Based on the documentation I have found, there is no mention of an "endpointUrl" or any alternative parameter for specifying a custom S3-compatible endpoint (such as MinIO) in Vapi's storage configuration—only standard AWS S3 parameters are documented. To help clarify your issue: Are you able to successfully configure and use AWS S3 storage with the same credentials and parameters (minus the endpointUrl), or does the problem only occur when you attempt to use your MinIO server? This will help determine if the issue is with custom endpoint support or with the credential validation process itself. Sources: - [Vapi S3 Provider Documentation](https://docs.vapi.ai/providers/cloud/s3) - [Provider Keys Documentation](https://docs.vapi.ai/customization/provider-keys)

@User @User

Hi Roman, To ensure HIPAA compliance on Vapi's platform, you need to enable the

hipaaEnabled

configuration in your assistant's settings. Here’s how you can do it: 1. **JSON Configuration**: Set

hipaaEnabled: true

in your assistant's configuration:

json
   {
     "hipaaEnabled": true
   }

2. **Provider Selection**: Make sure you use only HIPAA-compliant providers for model, voice, and transcription services like OpenAI, Azure, Deepgram, etc. 3. **Data Handling**: With HIPAA enabled, no call logs, recordings, or transcripts will be stored. For further details, you can check the [HIPAA Compliance documentation](https://docs.vapi.ai/security-and-privacy/hipaa).