-
Notifications
You must be signed in to change notification settings - Fork 247
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
Deploy Sagemaker "Serverless" option fails with error "Image size 13279248421 is greater than supported" #691
Comments
@jeve7 thanks for your report, we will take a look at it and get back to you |
Hi @jeve7 , So I just deployed the v5.5.0 version by cloning the github repo and the SagemakerEmbeddingsStack deployment succeeded for me. Are referencing the model here? :
Also I believe in a previous issue you mentioned you were migrating from v5.4.5 so could it be you have modified something that could be causing this? I would recommend trying out with a fresh new deployment to see if that succeeds for you and follow the readme when deploying. This should differentiate if it's an issue with some modified changes you might have. |
Interesting... thanks for the info. I did a brand new deployment twice using the public template from here: https://docs.aws.amazon.com/solutions/latest/qnabot-on-aws/step-1-launch-the-stack.html. I clicked the "Launch" link and that opens CloudFormation. I changed the region to "ca-central-1" and move forward. It failed twice with the same message when I selected "SagemakerInitialInstanceCount = 0". The second time I changed the rollback setting to be able to see the real error in the Sagemaker stack. |
I also have experienced the same issue. @bios6 it wasn't clear from your response, but did you try setting |
Hi @jeve7 |
Sounds good, thanks for the info @fhoueto-amz. |
Closing this as Serverless is not deployable. Our documentation in the next release will be updated to mention that. |
Describe the bug
I am trying to deploy the latest version (5.5.0) in a DEV environment so I am selecting "Serverless" for Sagemaker (SagemakerInitialInstanceCount = 0). The deployment is failing with the message: "Image size 13279248421 is greater than supported size 10737418240" when is creating the Sagemaker endpoint. I guess this problem is new in 5.5.0 since I did the same previously using 5.4.5 and it worked fine.
To Reproduce
Expected behavior
Deployment should work and Sagemaker will be configured as Serverless (Same as in 5.4.5) or the label/documentation is updated and Serverless is no longer an option meaning 1 Sagemaker server is the smallest available footprint.
Please complete the following information about the solution:
Screenshots
CloudFormation message:
The text was updated successfully, but these errors were encountered: