sagemaker-run-notebook icon indicating copy to clipboard operation
sagemaker-run-notebook copied to clipboard

Published 20 hours ago • verified publisher icon aws-samples

Getting timeout from Lambda RunNotebook when starting to run notebook

Open grossamit opened this issue 3 years ago • 2 comments

Happening a lot. I found a workaround to manual update the lambda configuration timeout ,wait 30sec and run again. In case I don't do this process ,then I usually need to wait for ~40min for the lambda to be "released" and work again. Any idea how to fix it? Maybe adding a Retry mechanism build in?

grossamit avatar Jan 05 '22 07:01 grossamit

Have you modified the Lambda config in any way from the CloudFormation in this package? Did you add VPC configuration to it?

tomfaulhaber avatar Jan 05 '22 17:01 tomfaulhaber

No. I've modified it manually every time it happens. Regarding VPC, sometimes I add it and sometimes not, it also happens without any VPC config.

grossamit avatar Jan 07 '22 06:01 grossamit