Closed fredericgboutin-yapla closed 2 months ago
ha god.... somehow the AWS_REGION
got truncated so this is a problem on our side 😞
So, if anybody else see this issue, double-verify the region's value.
BTW, when debugging the code I saw that the vendor/aws/aws-sdk-php/src/EndpointDiscovery/EndpointDiscoveryMiddleware.php
has some logic to emit a nice message and to retry with the default endpoint upon error with a custom endpoint. I suppose it could have been nice to have something similar when an invalid endpoint URL is generated because of an invalid region.
Anyway... sorry for the noise.
Cheers,
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.
Describe the bug
This morning our automatic translation logic started reporting errors,
And sure enough
Looking at the doc - https://docs.aws.amazon.com/general/latest/gr/translate-service.html - the url should be
translate.ca-central-1.amazonaws.com
and nottranslate.ca-central.amazonaws.com
- aka it is missing the-1
So this issue is quite critical as ALL AWS Translate methods stopped working.
Expected Behavior
The AWS Translate Client should poke the proper url so it actually works
Current Behavior
The AWS Translate Client currently poke an invalid url so it fails
Reproduction Steps
Possible Solution
As per the doc - https://docs.aws.amazon.com/aws-sdk-php/v3/api/class-Aws.AwsClient.html#method___construct - I tried,
But it does NOT work.
You have to pass a full fledge provider,
Additional Information/Context
No response
SDK version used
3.321.0
Environment details (Version of PHP (
php -v
)? OS name and version, etc.)8.2