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

Support all Step Function task resources #1314

Closed
4 of 7 tasks
eladb opened this issue Dec 10, 2018 · 10 comments · Fixed by MechanicalRock/tech-radar#14 · 4 remaining pull requests
Closed
4 of 7 tasks

Support all Step Function task resources #1314

eladb opened this issue Dec 10, 2018 · 10 comments · Fixed by MechanicalRock/tech-radar#14 · 4 remaining pull requests
Assignees
Labels
@aws-cdk/aws-stepfunctions Related to AWS StepFunctions feature-request A feature should be added or improved. in-progress This issue is being actively worked on. management/tracking Issues that track a subject or multiple issues

Comments

@eladb
Copy link
Contributor

eladb commented Dec 10, 2018

At the moment, step functions only support Lambda and Action, it would be awesome to add support for the rest of the resources as described here: https://docs.aws.amazon.com/step-functions/latest/dg/connectors-supported-services.html:

Namely:

  • AWS Batch
  • Amazon DynamoDB
  • Amazon ECS/Fargate
  • Amazon SNS
  • Amazon SQS
  • AWS Glue
  • Amazon SageMaker
@rix0rrr rix0rrr added feature-request A feature should be added or improved. @aws-cdk/aws-stepfunctions Related to AWS StepFunctions labels Dec 10, 2018
@rix0rrr rix0rrr added the gap label Jan 4, 2019
@0xdevalias
Copy link
Contributor

Curious if there is any known ETA/vague roadmap on this? In particular, interested in AWS batch (for this project), and ECS/Fargate (for future projects)

@eladb
Copy link
Contributor Author

eladb commented Feb 24, 2019

See #1646 #1275

rix0rrr pushed a commit that referenced this issue Jun 12, 2019
Have updated the package `@aws-cdk/aws-stepfunctions-tasks` to include support for SageMaker APIs as per documentation here: https://docs.aws.amazon.com/step-functions/latest/dg/connect-sagemaker.html

Includes support for the following Amazon SageMaker API calls:
* `CreateTrainingJob`
* `CreateTransformJob`

Partially remediates #1314
ScOut3R pushed a commit to ScOut3R/aws-cdk that referenced this issue Jun 13, 2019
Have updated the package `@aws-cdk/aws-stepfunctions-tasks` to include support for SageMaker APIs as per documentation here: https://docs.aws.amazon.com/step-functions/latest/dg/connect-sagemaker.html

Includes support for the following Amazon SageMaker API calls:
* `CreateTrainingJob`
* `CreateTransformJob`

Partially remediates aws#1314
@ymwdalex
Copy link

I am curious when glue job can be supported here?

@SomayaB SomayaB added the management/tracking Issues that track a subject or multiple issues label Sep 26, 2019
@moserda
Copy link

moserda commented Oct 9, 2019

Support for Glue jobs would also be highly appreciated from my side!

@rix0rrr
Copy link
Contributor

rix0rrr commented Oct 10, 2019

This is open for contribution. We are not currently working on this.

@wildcardops
Copy link

Support for batch would be super helpful to our team.

@tomomano
Copy link

Another vote for the support for batch!

@rix0rrr rix0rrr assigned nija-at and unassigned rix0rrr Jan 23, 2020
@abdullahodibat
Copy link

Also for me there is a need for Batch Support. is it going to be implemented soon?

@ayush987goyal
Copy link
Contributor

Hi, I have created a PR for adding Batch Support #6396

@SomayaB SomayaB added in-progress This issue is being actively worked on. and removed gap labels Feb 21, 2020
@nija-at
Copy link
Contributor

nija-at commented Feb 26, 2020

In an effort to break this further and track implementation of each separately, and, to track the +1s better, I've created separate tasks for the remaining items here -

If you're still waiting for any of these, kindly transfer your +1s to these separate issues. Thanks in advance!

@nija-at nija-at closed this as completed Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment