Closed jvanbuel closed 2 years ago
Hi @jvanbuel,
Thanks for raising this. The endpoints file is autogenerated, so any pull requests there would be overwritten later anyways. Thanks! The endpoints can be automatically inferred without being in the endpoints file, hence why you still get one when you instantiate a client. However knowing ahead of time which regions are supported is useful. I'm going to check in with the SageMaker team to clarify.
Generally you can also read about service endpoints in the documentation, but I don't see any for A2I either:
V337343631
Greetings! It looks like this issue hasn’t been active in longer than one year. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.
Describe the bug
When using
get_available_regions
api for the 'sagemaker-a2i-runtime' service, no regions / service endpoints are returned. I believe the underlying reason is that the service is not yet included inbotocore/botocore/data/endpoints.json
. Instead of submitting a PR to edit this file, I am submitting this issue, as suggested by the Contributing guide.Steps to reproduce
returns an empty list
[]
Expected behavior
I expected to receive a list of available regions and endpoints. The following boto3 snippet does allow me to list endpoints for the service:
returns
'https://a2i-runtime.sagemaker.eu-west-1.amazonaws.com'
Debug logs