You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, the arn:aws:states:::sagemaker:createProcessingJob.sync task is useful for users because it waits for the processing job to complete - whereas just using an AWS service/SDK sagemaker:createProcessingJob step would require additional states to monitor job status.
There were some previous attempts to get a solution merged in 2020 by @heatsink, but seems like a design was not agreed and to my understanding this RFC process would be the next step to make that happen(?)
API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
Kick off meeting
RFC pull request submitted (label: status/review)
Community reach out (via Slack and/or Twitter)
API signed-off (label api-approved applied to pull request)
Final comments period (label: status/final-comments-period)
Approved and merged (label: status/approved)
Execution plan submitted (label: status/planning)
Plan approved and merged (label: status/implementing)
Implementation complete (label: status/done)
Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.
The text was updated successfully, but these errors were encountered:
Closing this ticket. We believe the functionality is beneficial, but does not intersect with the core framework and should be vended and maintained separately.
Description
As described in aws/aws-cdk#9537, the
aws-cdk-lib/aws-stepfunctions-tasks
package currently implements task states for some of the optimized SageMaker service integrations such asSageMakerCreateModel
andSageMakerCreateTrainingJob
, but not for the sagemaker:createProcessingJob task.In particular, the
arn:aws:states:::sagemaker:createProcessingJob.sync
task is useful for users because it waits for the processing job to complete - whereas just using an AWS service/SDKsagemaker:createProcessingJob
step would require additional states to monitor job status.There were some previous attempts to get a solution merged in 2020 by @heatsink, but seems like a design was not agreed and to my understanding this RFC process would be the next step to make that happen(?)
Roles
Workflow
status/proposed
)status/review
)api-approved
applied to pull request)status/final-comments-period
)status/approved
)status/planning
)status/implementing
)status/done
)The text was updated successfully, but these errors were encountered: