Hi @limpid basin. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#Web ACLs issue
willow badgerBOT
limber ravenBOT
Hey there! This channel allows you to ask Kapa.ai for assistance. But it looks like you haven't connected your Discord profile to your Deepgram account yet. You can do so at https://community.deepgram.com - by doing so, you'll be able to ask questions in #1115960287183511643 if you need human assistance!
willow badgerBOT
The issue you're experiencing seems to be related to the AWS Web ACLs blocking incoming requests from Deepgram due to a missing user agent. However, the code snippet you provided is for setting a custom user agent when making requests to Deepgram, not for incoming requests from Deepgram.
Deepgram's callback requests do not originate from a set range of IP addresses due to the elastic cloud infrastructure that Deepgram leverages. Therefore, whitelisting specific IP addresses may not be a viable solution source (https://deepgram.gitbook.io/help-center/faq/how-do-i-validate-a-callback-request).
To validate incoming callback requests from Deepgram, you can use the request_id that is returned when a transcription job is created. By comparing the request_id in the callback request to the request_id returned in the original request, you can ensure that the callback request is legitimate source (https://deepgram.gitbook.io/help-center/faq/how-do-i-validate-a-callback-request).
If your internal network environment requires you to allow only specific IP addresses to access your network, another method would be to set up a proxy outside of your network to receive Deepgram's callbacks. This way, you can whitelist the IP address of the proxy server and allow it to access your internal network while keeping the rest of your network secure source (https://deepgram.gitbook.io/help-center/faq/how-do-i-validate-a-callback-request).