AWS Step Functions Reviews & Product Details

What I like best about AWS Step Functions is how easily it orchestrates complex workflows across AWS services with a visual, serverless approach. It simplifies coordination between multiple services while improving visibility into workflow execution and failures. I also appreciate the visual workflow management and the built-in retry and error-handling capabilities, which make complex orchestration easier to understand, maintain, and monitor. Review collected by and hosted on G2.com.

Complex state machine definitions can become hard to manage as workflows grow larger. Debugging deeply nested workflows can also be challenging, and handling more advanced error scenarios may take additional effort and careful attention. Review collected by and hosted on G2.com.

What I like most about AWS Step Functions is that it allows you to model complex workflows visually and in a controlled manner, without having to handle all the orchestration logic manually in code. It is especially useful for coordinating processes between various AWS services, such as Lambda, Glue, EventBridge, and other components of the ecosystem. I also greatly value the traceability of executions, error handling, retries, and the ability to define more robust and maintainable flows. For batch processes, automations, and data pipelines, it provides a lot of order and operational visibility. Review collected by and hosted on G2.com.

What I like the least is that, although the visual design helps a lot, the flows can become difficult to maintain when they grow significantly in complexity. In large scenarios, the definition in JSON can become extensive and less convenient to manage. There is also an initial learning curve to fully understand states, transitions, error handling, and service limits. Additionally, when a workflow depends on several external services or permission configurations, troubleshooting can take time. Review collected by and hosted on G2.com.

I would say step function is best to implement cascading lambdas, in my project we had requiremnt of having a cascading execution of code, where we broke down each functionality into lambdas and then used amazon's step function to execute it in a flow. Review collected by and hosted on G2.com.

The complexity is sometime more related to yaml/json. But now a days due to AI and co-pilot that is also easy. Review collected by and hosted on G2.com.

It’s easy to visualize and manage serverless workflows. The built-in error handling and retry logic also make it straightforward to deal with failures. Review collected by and hosted on G2.com.

The pricing can get more expensive as you scale. Review collected by and hosted on G2.com.

I liked how AWS Step Functions have a detailed execution flow for each of my other AWS resources., also I liked the feature of how without the help of lambda I can quickly call Dynamodb and do the operation, this helps in reducing resources and saving some bucks. Review collected by and hosted on G2.com.

So far not but earlier sometimes put a little more effort into writing step definitions thanks to WorkFlow Studio, the features to drag and drop AWS resources are pretty easy to use. Review collected by and hosted on G2.com.

It is easy to create an ETL flow in this service. It provides a feature to create workflow visually; in the back-end, it makes the whole JSON according to the visually prepared flow. Review collected by and hosted on G2.com.

The one of states provided in creating the flow is parallel state in which we can run multiple states simultaneously. But the drawback of this state is that if one of the entities fail, all the other entities included are aborted. Review collected by and hosted on G2.com.

The way we can utilize the state machines to reduce the load on lambda functions. By creating a proper flow between state machines we can handle multiple lambdas at once and achieve our goal efficiently. Review collected by and hosted on G2.com.

Only thing is we need to learn the state language which I think is new and not useful anywhere other than here. Review collected by and hosted on G2.com.

It's a low code workflow tool by AWS; we used the Step function to orchestrate the business process, which should run on the AWS cloud when a file is uploaded to S3 storage. We liked it as of use; you can have many connectors or AWS lambda functions as input/output. The output of a step can be quickly sent to another one. 100's of Connectors can be easily added via drag n drop. Review collected by and hosted on G2.com.

To be more proficient in the AWS step function, you should have a good command of the AWS Services & AWS ecosystem, so there is some learning curve involved for a novice developer. No offline/on-prem IDE's available to develop & deploy the AWS Step functions. Review collected by and hosted on G2.com.

Ability to integrate various AWS services for orchestration purposes, its visual workflow design is very easy to use to automate pipelines in the AWS environment. Review collected by and hosted on G2.com.

Aws service quotas with step functions sometimes break the whole design of the processes when there is large data processing or several jobs increase or the need to implement more parallelism increases. Review collected by and hosted on G2.com.

The best thing about step functions is it allows me to focus on building business logic and less time on integration code as it takes care of all internal application components. Review collected by and hosted on G2.com.

There are few limits on AWS Step functions as AWS manages them. It only allows to move of data of 256KB through workflows, and 90 days of execution history is retained, which is much less compared to its competitor. Review collected by and hosted on G2.com.