Is it possible to store the call recordings on an S3 compatible storage like Wasabi?

@froggy Absolutely! VAPI does support integration with various storage solutions, including S3-compatible services like Wasabi. You can configure your VAPI settings to send call recordings directly to your Wasabi bucket. Just make sure to provide the necessary credentials and configure the correct endpoint URL for Wasabi in your VAPI storage settings. If you need assistance with the configuration process, please don't hesitate to ask!

@User How would I implement the call recordings tombe saved to my own wasabi (S3 compatible) bucket then?

Look at your settings in API

I had a look, at present it seems to only accept the Amazon S3 creds, however, I'd emailed support to enquire if they anticipate supporting the Wasabi S3 compliant storage - way cheaper and no egress charges either.

@froggy as of now only aws s3 is supported but you can create a feature request for it from here https://vapi.canny.io

Give me more information on this

@froggy Certainly! If you're interested in having VAPI support Wasabi, an S3-compatible storage service, you can submit a feature request through the VAPI feature request portal. Here's how you can do it: 1. Visit the VAPI feature request portal at https://vapi.canny.io. 2. Create an account or log in if you already have one. 3. Once logged in, click on the "Create Post" button to start a new feature request. 4. Provide a title for your request, such as "Support for Wasabi S3-Compatible Storage." 5. In the description, explain why you would like VAPI to support Wasabi, including benefits like cost savings and no egress charges. 6. You can also detail any specific features or functionality you're looking for, such as seamless integration with existing VAPI services. 7. Submit your feature request. After submitting, other users can view your request and vote on it if they also want the feature. The VAPI team will review the community's interest and may consider implementing the feature based on user demand and feasibility. If you need any further assistance or have additional questions, please let me know!

@Vapi Tell me more about integrating Amazon S3 storage API

@froggy Integrating Amazon S3 with VAPI for storing call recordings involves several steps. Here's a general overview of the process: 1. Amazon S3 Setup: - Create an AWS account if you don't already have one. - Go to the Amazon S3 console and create a new bucket where your call recordings will be stored. - Set up the necessary permissions for your bucket to ensure that VAPI can write to it. This typically involves creating an IAM (Identity and Access Management) user with programmatic access and attaching a policy that grants the necessary S3 permissions. 2. VAPI Configuration: - Log in to your VAPI dashboard. - Navigate to the settings or integration section where you can configure storage options. - Select Amazon S3 as your storage option. - Enter the required credentials, which include the Access Key ID and Secret Access Key of the IAM user you created, as well as the bucket name and the AWS region where your bucket is located. 3. Security Considerations: - Ensure that the IAM policy attached to your user is following the principle of least privilege, granting only the permissions necessary to perform the required actions. - Use SSL/TLS to encrypt data in transit between VAPI and Amazon S3. 4. Testing: - After configuring the integration, perform a test call to ensure that the recordings are being successfully uploaded to your S3 bucket. - Check the S3 bucket for the new recording file to verify that the integration is working correctly. 5. Maintenance: - Regularly monitor your S3 bucket for storage usage and costs. - Implement lifecycle policies if needed to archive or delete old recordings. If you need specific instructions or assistance with any of these steps, please let me know, and I'll be happy to help!

What are the minimum permissions needed for the API key?

@froggy For integrating Amazon S3 with VAPI to store call recordings, the minimum permissions needed for the API key (IAM user) are as follows: -

s3:PutObject

- To upload call recordings to the specified S3 bucket. -

s3:GetObject

- To retrieve call recordings if needed for playback or download. -

s3:DeleteObject

- To delete call recordings from the bucket if your application requires this functionality. Here is an example of an IAM policy that grants these minimum permissions for a specific S3 bucket:

json
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:PutObject",
                "s3:GetObject",
                "s3:DeleteObject"
            ],
            "Resource": "arn:aws:s3:::your-bucket-name/*"
        }
    ]
}

Replace

your-bucket-name

with the actual name of your S3 bucket. This policy ensures that the IAM user can only perform the specified actions within the defined bucket and cannot access other resources in your AWS account. Always ensure that you're following best security practices by granting only the permissions necessary for the task at hand. If you have any further questions or need additional assistance, feel free to ask!