curl works, presigned uri from AWS used to work. Now it doesn't. No useful error message.

[deantaylormax]

Which Deepgram product are you using?

Deepgram API

Details

I have been testing an application for weeks using the Deepgram API. It has been working well, even modifying the models I am using. Suddenly and without any useful error message, as of a few days ago, my presigned uri from AWS does not yield a transcript from Deegram's API. My lambda function sending that file to the api just times out. No useful error message from Deepgram that my credentials are bad or the file format is bad, etc. I have been using the same four or five files for testing and they have repeatedly worked in the past. Ideas? I am going to have to move off of Deepgram if this is not resolved soon. Cannot afford more down time with no useful error message as to why.

If you are making a request to the Deepgram API, what is the full Deepgram URL you are making a request to?

No response

If you are making a request to the Deepgram API and have a request ID, please paste it below:

No response

If possible, please attach your code or paste it into the text box.

This is the AWS generated presigned uri which has consistently worked when generated. Now it does not. This is only useful for 60 minutes from generation per AWS security policy, but the format is the same when each one is generated.

this is the presigned_url https://deepgram-api-test.s3.amazonaws.com/moviespeechgladiator4.mp3?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAYSG3P7FM7LNTWNHX%2F20230702%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20230702T170436Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEHEaCXVzLWVhc3QtMiJGMEQCIGFB%2BPQQcQlHHCEMOybGbPMrZDEgexDpGU0TFHQcvEaMAiAu5rmrkFXf6syPjQZDbGOxwaCvKVUdgiU7XZitNG1XQCrxAgja%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F8BEAAaDDU4ODg3MDg0MjcxMyIMMapUDcZPfuekDg6PKsUCmSP8wr%2FgyqUBjMKR4jdRGHp%2FJ3vJ6dvFCSYqQXFn4VyIjy9jJI5ZMbxPBK2psWZdaa4xq3B8cV2kA%2BcC545y7nAnxHHzz7bUX29Pq1TeVkwIbzggHQ3rAdLH71ZNgqL6ExwBNbJ%2Bs6vuLJvS0AE2u02eRPr3qWJPXuCezFfVq0WPkCBSOffPZw8JJ6nmp6uZQJ1X%2BU%2BsZGQ7u7ELHdvk2ULghkOnabcOcVVsNxEWApPfSng3pX1xfRjUCs1N4jwmPf%2BPZ9goOoxpJ9OKbs7gPnHl9vhYLY%2FNiFnbeF4lU3efiDoAWFNnHeysfFOL37YkyB7wzHCwaUGY%2BIk81aL%2FQoIDEFtaA95M%2FQnN00NCs793P2nLoRIGe4ityRtt2y3OK8gwQyhlUCPYk%2FRVVkrFsraBBJFgonarznQ2XfQLQQmgVKtEZjDr2oalBjqfAVQLQ%2BFJog6n5DHx8kgf8XiPy3FI5mRjZd8CEK5tekrKvIzAUKS0s0ANV5Z%2Fj4IaVeFQispnPwmNd4Jm0gI2VkG0gHDbvaX%2Fz%2Fndk6xWKYUL7c0SbDl%2BE1nRvlzM2tnUPi6gejDKzgKObJ7gMds74CqZyumwj17edNysnwNGpf5DvpfjuBXQdZYnnGWQreTQnRKqknBDjsKEHhNmteBSdw%3D%3D&X-Amz-Signature=714d666b36df5ab0b8564114d32282a89062555af0dc7a359dd6e48436e465d3

If possible, please attach an example audio file to reproduce the issue.

Tried to attach the mp3 file and got error message that you do not support this file type. Is this something new then?

[jkroll-deepgram]

Hi @deantaylormax, I'm sorry that this error has cropped up. I don't know of any recent changes to the Deepgram product that would affect your ability to use a pre-signed URI to receive transcripts. I'm hearing that you're using the same Lambda code and test files, correct? The fact that you're not seeing any permission errors would lead me to conclude that this isn't an issue with AWS IAM permissions, pre-signed URL expiration, or Deepgram API key. Are you getting Deepgram request IDs back? If so, please share one and I will look into how the request is being processed on our side.

I understand that your code has been working, but it may help to read over our guide on Using AWS S3 Presigned URLs with the Deepgram API, to see if it mentions some detail that is a clue to what may be going wrong here.