Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Policy template for sending task status to Step Functions #2193

Closed
gevial opened this issue Oct 25, 2021 · 4 comments
Closed

Policy template for sending task status to Step Functions #2193

gevial opened this issue Oct 25, 2021 · 4 comments

Comments

@gevial
Copy link

gevial commented Oct 25, 2021

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.

@gevial
Copy link
Author

gevial commented Oct 25, 2021

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 Resources: "*" for this policy.

@gevial
Copy link
Author

gevial commented Oct 25, 2021

Here's a PR: #2194

@mildaniel
Copy link
Contributor

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.

@bluenautilus2
Copy link

Looking forward to this!

@aws aws locked and limited conversation to collaborators Aug 8, 2023
@aaythapa aaythapa converted this issue into discussion #3288 Aug 8, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

5 participants