Closed mstfldmr closed 4 years ago
Hi @mstfldmr I haven't been able to recreate this issue. Can you confirm if it's still occurring and the steps you've taken to reach this? Thanks!
Additionally note my last comment from Issue #6
Note: the AWS Solution will be officially updated early next week. Code is merged into GitHub in the meantime. To use this code, you'll need to git clone this repository into SageMaker, for example via the terminal or using Git integration. Feel free to ping me if you have questions.
Hi @mstfldmr, we were able to re-create the issue. A fix has been checked in and is being deployed to the official soln. You can git clone within your workspace to pull the latest code.
Commit 52b85fe**
This fix is now released on the official solution page on AWS solutions so you can redeploy from there: https://aws.amazon.com/solutions/implementations/predictive-maintenance-using-machine-learning/. Alternatively you can use the quick-launch button in the README of this repository to get the latest version via github.
Lambda execution creates this Cloudwatch log:
This role does not exist, but another one (PredMaint-SolutionBuilder-NotebookInstanceExecutio-EP4DFXR5ZUO6) was created by the Cloudformation template.