EPM Practice Manager at a tech services company with 1,001-5,000 employees
Real User
Top 5
2025-04-01T17:53:43Z
Apr 1, 2025
I am not familiar with the pricing as most of my projects have environments from the customer side, and the contract-related issues are not my responsibility.
Pricing for Step Functions is very cheap. On a scale from one to ten, I rate it as three in terms of costs, with one being the most affordable. It is cost-effective.
The solution is expensive. It is worth the money. AWS offers event bridges. Another service triggers any job and provides event buses to fasten parameters. For data lakes, event buses are very useful for obtaining keys for each file. Compared to Step Functions, the pricing is much higher, especially when moving from static infrastructure machines. The pricing model should be based on OpenEdge plans.
Solution Architect at a comms service provider with 11-50 employees
Real User
Top 10
2023-09-14T11:53:33Z
Sep 14, 2023
We went for the Step Functions service. The pricing for Step Functions was quite convoluted and difficult to understand due to the numerous small factors involved, such as data transfers and limitations on runtimes. Additionally, replacing existing Step Functions tasks was not straightforward. As a result, we opted for a solution that provided clear and understandable outputs, allowing us to effectively monitor and manage our workflows. For we went for Lambda function for more decent output and to see what was going on. It was more Amazon API for infrastructure. We were trying some EFS-related stuff and some proprietary APIs from Amazon. So, pricing depends on what I am doing. If you're consuming two or three things a day, it's fine. It's cheap. But then there's no price control because Amazon is about, "Let me help you consume as much as possible," so then I can be, like, hell at the end of the month.
I am unsure about the price, but I remember they were charging 0.25 cents for our conversions. For example, you're always charged based on the number of requests in your workflow and the duration. For example, it could be $1 per 1 million requests.
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,...
I am not familiar with the pricing as most of my projects have environments from the customer side, and the contract-related issues are not my responsibility.
Pricing for Step Functions is very cheap. On a scale from one to ten, I rate it as three in terms of costs, with one being the most affordable. It is cost-effective.
The cost is average, provided it is configured correctly. AWS charges for active usage periods.
The solution is expensive. It is worth the money. AWS offers event bridges. Another service triggers any job and provides event buses to fasten parameters. For data lakes, event buses are very useful for obtaining keys for each file. Compared to Step Functions, the pricing is much higher, especially when moving from static infrastructure machines. The pricing model should be based on OpenEdge plans.
The pricing for Amazon Step Functions is flexible and depends on the usage of the product. It is cheaper than Azure Workflow.
We went for the Step Functions service. The pricing for Step Functions was quite convoluted and difficult to understand due to the numerous small factors involved, such as data transfers and limitations on runtimes. Additionally, replacing existing Step Functions tasks was not straightforward. As a result, we opted for a solution that provided clear and understandable outputs, allowing us to effectively monitor and manage our workflows. For we went for Lambda function for more decent output and to see what was going on. It was more Amazon API for infrastructure. We were trying some EFS-related stuff and some proprietary APIs from Amazon. So, pricing depends on what I am doing. If you're consuming two or three things a day, it's fine. It's cheap. But then there's no price control because Amazon is about, "Let me help you consume as much as possible," so then I can be, like, hell at the end of the month.
The solution's price is reasonable.
I am unsure about the price, but I remember they were charging 0.25 cents for our conversions. For example, you're always charged based on the number of requests in your workflow and the duration. For example, it could be $1 per 1 million requests.