-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(aws-scheduler-targets-alpha): Add SageMakerStartPipelineExecution Target #27457
Comments
Thank you for all those feature requests and PRs! |
|
I am trying to use import aws_cdk.aws_sagemaker as sagemaker
# pipeline: sagemaker.IPipeline
Schedule(self, "Schedule",
schedule=ScheduleExpression.rate(Duration.minutes(60)),
target=targets.SageMakerStartPipelineExecution(pipeline,
pipeline_parameter_list=[targets.SageMakerPipelineParameter(
name="parameter-name",
value="parameter-value"
)]
)
) However, I fail to understand how to create the Can you clarify if the example code from the README is supposed to work with the current release of CDK? If yes, how can I create an instance of Side note: The sagemaker python sdk has support to attach EventBridge schedules to SageMaker Pipeline, however it can't take any parameter (so only pipeline executions with default parameters are possible), plus, it's not compatible with Local Mode, and the schedule does not make its way into the Pipeline definition, and creates the rules ad-hoc (before upsetting the pipeline), so if I create the pipeline definition with the sagemaker python sdk and then use this definition in cdk / cfn, I loose the schedule. Hence, there seems to be no way to schedule Pipeline Executions with non-default parameters with CDK or the sagemaker sdk. I'd appreciate your help (maybe this needs a new issue?) and allow myself to tag the relevant people as described in the comment visibility warning @kaizencc, @pahud, @filletofish. |
Hi @lorenzwalthert , could you create a separate issue if this is still relevant? As we don't usually look at closed issues (I just happened to stumble across this). Thank you! |
Describe the feature
Work to support L2 constructs for AWS Scheduler is in progress (#23394). See the approved RFC. RFC planned to add 12 templates targets, but only Lambda Invoke is currently implemented (#26575).
This issue tracks implementation of
SageMakerStartPipelineExecution
target to start Amazon SageMaker pipeline.Use Case
Customers would like to use templated target
SageMakerStartPipelineExecution
to be able to start an Amazon SageMaker pipeline on schedule. L2 target construct should grant required permissions to theAWS Scheduler
to start an Amazon SageMaker pipeline.Proposed Solution
The proposed solution needs to be adopted to the recent examples of
LambdaInvoke
(https://github.com/aws/aws-cdk/blob/main/packages/%40aws-cdk/aws-scheduler-targets-alpha/lib/lambda-invoke.ts).Solution should also include unit and integration tests.
Class
SageMakerStartPipelineExecution
should:addTargetActionToRole
bindBaseTargetConfig
to returnsageMakerPipelineParameters
as part ofScheduleTargetConfig
.Other Information
No response
Acknowledgements
CDK version used
2.99.1
Environment details (OS name and version, etc.)
MacOS
The text was updated successfully, but these errors were encountered: