Amplify teams hand-wire Step Functions and lack editing tools
AWS developers building Amplify apps reported that the CLI workflow did not handle Step Functions, pushing them to add CloudFormation manually or manage a separate Terraform workflow. Other Step Functions developers wanted a graphical way to create and edit workflow models, including values linked to their AWS accounts. Together, the signals point to a fragmented authoring and deployment workflow, though they come from requests posted between 2018 and 2021.
For AWS Amplify and Step Functions developers. Mentioned from Nov 2018 to May 2021 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I'm currently manually integrating the CloudFormation behind the scenes, or alternately using Terraform as a completely separate side application which then gets called from Amplify Apps
I make step-functions working by creating a "Custom CloudFormation stacks". Similar to this this but for using Step Functions as orchestration instead of SNS topics for monitoring
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks