I enabled the cloud storage for audio recordings and since I have enabled it, I can no longer listen my recordings through the VAPI dashboard. Is this intentional? I haven't enabled any sort of hippa compliance flags or anything else of that nature.

Hi there! 👋 I don't have definitive confirmation on whether this behavior is intentional, but I can share what I know about how cloud storage affects recordings in VAPI. Based on the information I found, it appears that enabling S3 recording likely impacts how recordings are stored and accessed. When you enable cloud storage for audio recordings, the recordings are uploaded to your S3 bucket after the call ends, rather than being stored in VAPI's default storage system (Cloudflare R2). According to the documentation I found, "Your assistants can be configured to record chat conversations and upload the recordings to a bucket in AWS S3 when the conversation ends" and "if no cloud storage or webhook is specified, recordings and transcripts are permanently deleted to avoid retaining sensitive data." This suggests that enabling cloud storage might redirect recordings exclusively to your S3 bucket, potentially making them unavailable through the dashboard. By default, Vapi stores recordings in Cloudflare R2, but when you configure it to use your own bucket in AWS S3, it appears the recordings are then only available in that external storage location rather than through the dashboard's native playback feature. Would you like me to help you explore any workarounds or alternative ways to access these recordings? Sources: - [Impact of enabling S3 Recording on VAPI dashboard audio playback](https://docs.vapi.ai/providers/cloud/s3) - [VAPI dashboard audio playback when using cloud storage for audio recordings](https://docs.vapi.ai/security-and-privacy/pci) - [What is cloud storage for audio recordings in Vapi?](https://docs.vapi.ai/customization/provider-keys)

VAPI can't listen to or make recordings audible when you store them on your cloud storage by default. They're stored locally and aren't publicly accessible. You can't hear them through the dashboard, but you can give read access to the recordings if you change your access policy.

@User can you send an example policy for this

This policy grants read access to the objects in your bucket. Replace

YOUR_BUCKET_NAME

with the name of your S3 bucket. \`\`\`json { "Version": "2012-10-17", "Statement": \[ { "Sid": "AllowPublicReadAccess", "Effect": "Allow", "Principal": "\*", "Action": "s3:GetObject", "Resource": "arn:aws:s3:::YOUR_BUCKET_NAME/\*" } \] } \`\`\` Here’s how to apply this policy: 1\. Open the Amazon S3 console. 2\. In the Bucket name list, choose the name of the bucket that you want to set the policy for. 3\. Choose the Permissions tab. 4\. In the Bucket policy section, choose Edit. 5\. Copy and paste the above policy into the Bucket policy editor, replacing

YOUR_BUCKET_NAME

with the name of your bucket. 6\. Choose Save to apply the policy. This policy allows anyone to read the objects in your bucket. If you need more restrictive access (e.g., only specific users or roles), you can adjust the

Principal

field accordingly. If you have any further questions or need additional assistance, feel free to ask!