Skip to content
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

Add Step Functions SageMaker CreateProcessingJob task construct #509

Closed
1 of 11 tasks
athewsey opened this issue May 31, 2023 · 1 comment
Closed
1 of 11 tasks

Add Step Functions SageMaker CreateProcessingJob task construct #509

athewsey opened this issue May 31, 2023 · 1 comment
Labels

Comments

@athewsey
Copy link

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 as SageMakerCreateModel and SageMakerCreateTrainingJob, 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/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(?)

Roles

Role User
Proposed by @athewsey
Author(s)
API Bar Raiser
Stakeholders

See RFC Process for details

Workflow

  • Tracking issue created (label: status/proposed)
  • 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.

@evgenyka evgenyka added the l2-request request for new L2 construct label Oct 11, 2023
@awsmjs
Copy link
Contributor

awsmjs commented Dec 14, 2023

Closing this ticket. We believe the functionality is beneficial, but does not intersect with the core framework and should be vended and maintained separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants