## What this teaches

How to outputKey in start_transcription_job() cant have =.

## The problem

Issue boto/boto3#4312 (closed, 6 comments): ### Describe the bug

An error occurs when calling the `start_transcription_job()` operation in AWS Transcribe with an OutputKey containing an equals sign (`=`). 
This leads to a BadRequestException, even though S3 allows keys with "=".

**Error**
```
An error occurred (BadRequestException) when calling the StartTranscriptionJob operation: 1 validation error detected: Value 'name=name/stage=prod/2b32d9cd6ce13621d332e1ae23d7a7ba.json' at 'outputKey' failed to satisfy constraint: Member must satisfy regular expression pattern: [a-zA-Z0-9-_.!*'()/]{1,1024}$ 

``` 

### Regression Issue

-...

## What worked (verified answer)

StartTranscriptionJob rejects an OutputKey containing `=` with BadRequestException: the output key must match [a-zA-Z0-9-_.!*'()/]{1,1024}. The reporter's workaround: write the transcription to a temp key and copy the file in S3 afterward. But note an AWS engineer re-tested with boto3 1.38.44 and the service accepted `=` on OutputKey, so upgrade boto3/botocore first; use the temp-key-and-copy workaround only if it still fails.

## Source

gh:boto/boto3#4312 - https://github.com/boto/boto3/issues/4312