Assistant Manager at a tech vendor with 10,001+ employees
Real User
Top 5
Aug 18, 2025
AWS Step Functions' fault tolerance capabilities can be improved, but if managed well in orchestration, then the impact is minimal. However, the product-wise capabilities could improve. Optimization regarding the fault tolerant capabilities of AWS Step Functions needs improvement. I do not have any other areas of AWS Step Functions I would like to see improved except for the fault tolerance aspect, as the failure and success aspects can be improved in how we implement it in the flow.
EPM Practice Manager at a tech services company with 1,001-5,000 employees
Real User
Top 5
Apr 1, 2025
There is room for improvement in terms of integration with other products. It would benefit from more integration with different applications or services.
One area for improvement is the payload size. Currently, I sometimes have to save data as a file since I cannot pass it within Step Functions, necessitating caching in processes. Increasing the payload size would be beneficial.
If AWS Step Functions keeps adding more integrations, it would be even better. Otherwise, the UI is great, the functionality is great, and everything is great. AWS Step Functions already has many integrations, but adding more is always good for enterprises.
The solution's pricing could be cheaper. It is cheaper than Airflow. We cannot directly pass the parameters of any SQL, emails. It is a simple state, but if they provide any coding platform inside, we need to make it more dynamic instead of drag and drop.
Senior Software Engineer at a tech services company with 11-50 employees
Real User
Top 10
Jan 29, 2024
There could be better integration with IDEs, such as more seamless access to credentials without needing daily updates. Additionally, it would be helpful to have better visibility into Step Functions, such as being able to view parallel executions within the same Step machine. Improved profiling and logging features would also enhance the management of processes. The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes. Having a desktop option might provide more detailed information, especially for teams like ours that need to validate multiple sub-functions concurrently. It would be beneficial to see these functions running in parallel for performance validation purposes.
In terms of improvement, I would like to see more data transformation features in Amazon Step Functions, like additional operators and logic, to enhance its capabilities in handling and transforming data during workflows.
Solution Architect at a comms service provider with 11-50 employees
Real User
Sep 14, 2023
It wasn't easy to understand the licensing model. It's like if you use just a little, it's cheap, but it becomes more expensive as you use more. It's like a hook that ties you inside the Amazon ecosystem. So, it creates a dependency. I don't like it because it creates a dependency, like Microsoft or other players who want you to stay within their ecosystem as much as possible.
The solution has a data limit of 256 KB which means you can only pass under 256 KB of data to a state machine and between its state transitions. This can be improved.
It is hard to coordinate the declaratory language, especially when you have it embedded. Furthermore, the limits are not to be controlled, and having a limit of 256 KB for the data could be much better.
AWS Step Functions integrate seamlessly with other AWS services to offer efficient pipeline and workflow management. Its intuitive design allows for streamlined orchestration, easily handling complex tasks.AWS Step Functions provide robust orchestration and automation capabilities, simplifying the creation of workflows with graphical and JSON-based designs. It excels in managing tasks through advanced parallelization and error handling features. Automatic scaling further enhances performance,...
AWS Step Functions' fault tolerance capabilities can be improved, but if managed well in orchestration, then the impact is minimal. However, the product-wise capabilities could improve. Optimization regarding the fault tolerant capabilities of AWS Step Functions needs improvement. I do not have any other areas of AWS Step Functions I would like to see improved except for the fault tolerance aspect, as the failure and success aspects can be improved in how we implement it in the flow.
There is room for improvement in terms of integration with other products. It would benefit from more integration with different applications or services.
One area for improvement is the payload size. Currently, I sometimes have to save data as a file since I cannot pass it within Step Functions, necessitating caching in processes. Increasing the payload size would be beneficial.
It is difficult to suggest improvements at the moment. No critical issues or pain points come to mind immediately.
If AWS Step Functions keeps adding more integrations, it would be even better. Otherwise, the UI is great, the functionality is great, and everything is great. AWS Step Functions already has many integrations, but adding more is always good for enterprises.
The solution's pricing could be cheaper. It is cheaper than Airflow. We cannot directly pass the parameters of any SQL, emails. It is a simple state, but if they provide any coding platform inside, we need to make it more dynamic instead of drag and drop.
There could be better integration with IDEs, such as more seamless access to credentials without needing daily updates. Additionally, it would be helpful to have better visibility into Step Functions, such as being able to view parallel executions within the same Step machine. Improved profiling and logging features would also enhance the management of processes. The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes. Having a desktop option might provide more detailed information, especially for teams like ours that need to validate multiple sub-functions concurrently. It would be beneficial to see these functions running in parallel for performance validation purposes.
In terms of improvement, I would like to see more data transformation features in Amazon Step Functions, like additional operators and logic, to enhance its capabilities in handling and transforming data during workflows.
It wasn't easy to understand the licensing model. It's like if you use just a little, it's cheap, but it becomes more expensive as you use more. It's like a hook that ties you inside the Amazon ecosystem. So, it creates a dependency. I don't like it because it creates a dependency, like Microsoft or other players who want you to stay within their ecosystem as much as possible.
The pricing of the solution can be improved.
The solution has a data limit of 256 KB which means you can only pass under 256 KB of data to a state machine and between its state transitions. This can be improved.
It is hard to coordinate the declaratory language, especially when you have it embedded. Furthermore, the limits are not to be controlled, and having a limit of 256 KB for the data could be much better.