Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

186
Vistas
Amazon Transcribe and Golang SDK BadRequestException

I uploaded a .flac file to an Amazon S3 bucket but when I try to transcribe the audio using the Amazon Transcribe Golang SDK I get the error below. I tried making the .flac file in the S3 bucket public but still get the same error, so I don't think its a permission issue. Is there anything that prevents the Transcribe service from accessing the file from the S3 bucket that I'm missing? The api user that is uploading and transcribing have full access for the S3 and Transcribe services.

example Go code:

    jobInput := transcribe.StartTranscriptionJobInput{
        JobExecutionSettings: &transcribe.JobExecutionSettings{
            AllowDeferredExecution: aws.Bool(true),
            DataAccessRoleArn:      aws.String("my-arn"),
        },
        LanguageCode: aws.String("en-US"),
        Media: &transcribe.Media{
            MediaFileUri: aws.String("https://s3.us-east-1.amazonaws.com/{MyBucket}/{MyObjectKey}"),
        },
        Settings: &transcribe.Settings{
            MaxAlternatives:   aws.Int64(2),
            MaxSpeakerLabels:  aws.Int64(2),
            ShowAlternatives:  aws.Bool(true),
            ShowSpeakerLabels: aws.Bool(true),
        },
        TranscriptionJobName: aws.String("jobName"),
    }

Amazon Transcribe response:

BadRequestException: The S3 URI that you provided can't be accessed. Make sure that you have read permission and try your request again.
over 4 years ago · Santiago Trujillo
1 Respuestas
Responde la pregunta

0

My issue was the audio file being uploaded to s3 was specifying an ACL. I removed that from the s3 upload code and I no longer get the error. Also per the docs, if you have "transcribe" in your s3 bucket name, the transcribe service will have permission to access it. I also made that change but you still need to ensure you aren't using an ACL

over 4 years ago · Santiago Trujillo Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda