- 新しい順
- 投票が多い順
- コメントが多い順
What you suggest is the right way to go at the moment, i.e., run the loop yourself and use a Choice state to check if the NextToken is empty as an exit criteria from the loop. If you need to do it in different places, maybe it is possible to do it with a nested workflow to run the loop.
Lambda supports up to 15 min execution time as of October 18, 2018. You could process the next tokens in the function itself.
We use the same technique: We want to load > 1 million data sets from a database and process it with different lambda functions and do some other stuff with it. Therefore, we use a choice state with a loop within the step functions and have an "iterator" step that is loading new data right after the choice.
Seems like I can not add an image here, I'm sorry :)
I would NOT go the way Rodney Lester suggests to do the looping in Lambda as you do not have retries over certain batches for example.
関連するコンテンツ
AWS公式更新しました 10ヶ月前
Looping by using the NextToken is currently not working within Step Functions and SDK Integration, since the NextToken only works within the same IAM Session, but Step Functions assumes a new IAM Session/Role at each SDK Integration step/task. So the workaround is to call a Lambda which calls the API and the handles possible NextTokens.