Repository navigation
Replies: 5 comments
|
According to https://docs.aws.amazon.com/step-functions/latest/dg/concept-create-iam-advanced.html, Step Function API calls to update task status require "the ARN of the activity or the token of the instance as part of the request". Since the token is provided as an input to the worker Lambda function, I think it's safe to use |
0 replies
|
Thank you for your contribution! We really appreciate it. Once a PR is submitted we weigh it against our roadmap, do regression testing, make sure it’s backwards compatible and maintainable. Please watch this channel from more updates, and feel free to reach out. |
0 replies
|
Looking forward to this! |
0 replies
|
Closing this as the PR to add this is merged. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description:
There is a pattern to coordinate queue-based Lambda function execution from a Step Function: https://aws.amazon.com/getting-started/hands-on/orchestrate-microservices-with-message-queues-on-step-functions/
The worker Lambda function in this approach needs to send task status back to the step function. Currently there is no ready-to-use policy for that in SAM.
I'm going to create a PR which adds the policy with states:SendTaskFailure, states:SendTaskHeartbeat and states:SendTaskSuccess permissions.
All reactions