Closed nfbalbontin closed 3 years ago
Hi @nfbalbontin,
In the first notebook 1_prepare_data/prepare_data.ipynb we set the SageMaker Python SDK version.
Make sure you have ran this command.
!pip install -q sagemaker==2.16.2
Can you confirm this solves the issue?
Hi! Thank you for the quick reply. I added a cell at the beginning of deploy_endpoint.ipynb
with the command you mentioned:
!pip install -q sagemaker==2.16.2
Still, it throughs the same error:
update_endpoint is a no-op in sagemaker>=2.
See: https://sagemaker.readthedocs.io/en/stable/v2.html for details.
And after, when I run all the following cells, I get the same error specified before.
After searching for the problem, I found the class sagemaker.predictor.Predictor
that can be used for real-time predictions against SageMaker endpoints, but you need to have a deploy made -If I'm correct-. Could it be possible to make the deploy after running creating the model in train_model.ipynb
? I tried with no success, but maybe I'm not getting the procedure right.
Did you restart the notebook kernel after updating the sdk? This should remove the warning.
Yes, I did. I even try with different kernels for the execution. Thanks again for the quick answer.
At the end it wasn't a problem related to the version. Thanks anyways!
Hi! I've been struggling for a while to deploy the model so then I can make predictions. When running:
I obtain the following error:
update_endpoint is a no-op in sagemaker>=2. See: https://sagemaker.readthedocs.io/en/stable/v2.html for details.
It still runs the statement. But afterwards, when executing:
It shows the following error:
ConnectionClosedError: Connection was closed before we received a valid response from endpoint URL: "https://runtime.sagemaker.us-east-1.amazonaws.com/endpoints/tf2-object-detection-2021-03-08-15-34-35-827/invocations".
Are there any ways to fix this problem? I tried fixing the
udpate_endpoint
but with no luck. Thanks!