You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an 11 year retention period in place for all files related to Amazon Connect, so these buckets become unmanageable very quickly.
By environment variable, it would be good to store these files similar to how Kinesis Firehose stores in S3, under yyyy/mm/dd/hh/{self.contact_id}.wav
I can make the change to the code after we pull it down, but that makes upgrades challenging. I'm not a Python coder or I'd offer to do a PR. My tweak will be hacky at best. :)
The same environment variable should also ensure the transcriptions are stored in the same location.
Thanks!
The text was updated successfully, but these errors were encountered:
PeifferWM
changed the title
Feature Request: Partitioned Storage of WAV
Feature Request: Optionally store Audio and Transcription under 'yyyy/mm/dd/hh'
Oct 15, 2024
Hello,
Currently the WAV files are stored in S3 at the root of the bucket.
We have an 11 year retention period in place for all files related to Amazon Connect, so these buckets become unmanageable very quickly.
By environment variable, it would be good to store these files similar to how Kinesis Firehose stores in S3, under
yyyy/mm/dd/hh/{self.contact_id}.wav
I can make the change to the code after we pull it down, but that makes upgrades challenging. I'm not a Python coder or I'd offer to do a PR. My tweak will be hacky at best. :)
The same environment variable should also ensure the transcriptions are stored in the same location.
Thanks!
The text was updated successfully, but these errors were encountered: