-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to run Amazon Augmented AI (A2I) and SageMaker Endpoint locally #5
Comments
I think I found the solution. But I still think it's a bug. The files seem to be too large. I'm using smaller sized pics and is working fine. The error message you get back, says nothing about it which is confusing. |
Ok, I discovered something else. Looks like if you rerun the notebook, the images double, triple in size (they become n times large with n the number of times you run the notebook). This fixes that problem: for ind in test_photos_index:
!rm sample-a2i-images/pexels-photo-{ind}.jpeg Maybe with bash magic we can check if the file already exists to NOT redownload it, but this is fine for me |
Hello @papagala, thanks for your feedback. Indeed the SageMaker error
could stem from image payload to the endpoint exceeding the limit 5MB. The original files are around 2-3 MB. Thanks for reporting that the curl would append the image and grow the file size. It's something we can address easily. We will also address the description for running environment. Thanks for your feedback again. |
Thanks a lot! |
Closing based on michaelhsieh42@'s merge |
Thank you all! |
It's a bit unclear how to run this locally, but managed to bypass errors around credentials not being found by passing a boto3.Session to the sagemaker.Session that calls one of my "profile_name"s.
However, I'm getting this error everytime I try to make a prediction. Specifically when I run
I get
If I run
results = object_detector.predict("dummy text")
I get something I can understand and expect:
Name: boto3
Version: 1.13.12
Name: sagemaker
Version: 1.58.2
Name: botocore
Version: 1.16.12
Python 3.7.3
The text was updated successfully, but these errors were encountered: