AWS CFT fix SageMaker Notebook lifecycle config #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Found this while some teammates were spinning up a Metaflow stack as part of a hackathon:
When deploying the AWS CloudFormation stack, if the SageMaker Notebook param is enabled there will be an error:
Digging into the SageMaker Notebook instance logs, we can find it's from this:
This looks to be due to SageMaker swapping from Amazon Linux 1 to Amazon Linux 2, with further discussion here aws-samples/amazon-sagemaker-notebook-instance-lifecycle-config-samples#76
After updating the lifecycle config for the new command, the stack was created successfully and notebook instance had the expected metaflow params preconfigured.