Creates a CloudFormation template that uses AWS StepFunctions to automate the building and training of Sagemaker custom models based on S3 and GitHub events
it does not really change much for this repository, we are already calling the sagemaker APIs through a lambda function. However, replacing those lambda api calls with the sagemaker integrations would
make the step function simplier by removing many of the looping logics
all training jobs to run over over 2 week. this current limit is due to step functions having a limit on how many state transitions there can be and the looping logic burns up most of those transitions for long running jobs and when you use the sagemaker integrations it counts as a single transition. I had a conversation with the step functions team awhile back on this topic and they agreed.
With the news about native integration with Step Functions, https://aws.amazon.com/about-aws/whats-new/2019/10/aws-step-functions-expands-amazon-sagemaker-service-integration/, Will there be changes coming to SageMaker Build based on this news?