3 ms·
A little friendly warning, about setting orchestrated logic with AWS Step Functions or similar third party solutions, particularly when calling Lambda functions
by belter 5y ago
A little friendly warning, about setting orchestrated logic with AWS Step Functions or similar third party solutions, particularly when calling Lambda functions.
Don't forget to setup your AWS billing alarms using AWS Budgets plus AWS Budget Actions. A standard best practice in any case.
Also enforce timeouts at the State Machine level:
https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-state-machine-structure.html https://docs.aws.amazon.com/step-functions/latest/dg/amazon-...
The reason being that, for a Lambda function, and independently of your execution logic, the Lambda execution in any case terminates, ( depending on configuration), in the worst case after 15 min. So also terminates the corresponding billing for that execution also.
With Step Functions or similar orchestration, a logic error could expose you to create an infinite loop of continuous invocations and the corresponding never ending growing invoice accompanying it :-)
- moltar 5y agoGood advice. But a small correction. Step Functions have a limit too. I think it’s 25,000 transitions per execution.