You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like due to aioboto3 enforcing the region, the endpoints deployed in regions other than us-west-2 (e.g. eu-central-1) fail and are not found. Is there a reason that us-west-2 is hardcoded here and here ?
This seems to have happened after 1.24 release.
Relevant log output
'An error occurred (ValidationError) when calling the InvokeEndpoint operation: Endpoint <ENDPOINT-NAME> of account <NR> not found.'
Hey @hooman-bayer no - this was not intentional, and was missed during the aioboto3 merge. Thanks for flagging it. I'll have this fixed by tomorrow and add more region testing for our acompletion endpoint.
What happened?
It seems like due to
aioboto3
enforcing the region, the endpoints deployed in regions other thanus-west-2
(e.g.eu-central-1
) fail and are not found. Is there a reason thatus-west-2
is hardcoded here and here ?This seems to have happened after
1.24
release.Relevant log output
'An error occurred (ValidationError) when calling the InvokeEndpoint operation: Endpoint <ENDPOINT-NAME> of account <NR> not found.'
Twitter / LinkedIn details
https://www.linkedin.com/in/hooman-s-449b0838
The text was updated successfully, but these errors were encountered: