1 Answers
0
The issue was actually caused by trying to provide the definition inside double quotes via the aws cli create-state-machine command when talking to AWS SFN and SFN Local.
Changing this to single quotes wrapping around the json unescaped has resolved this issue
Currently unsure what the issue is with the double quotes, but assuming it is some form of escaping that is required
answered a month ago
Relevant questions
Step Function Local Accessing Context Object causes SCHEMA_VALIDATION_FAILED
asked a month agohow to trigger a step function from a s3 object notification?
asked 4 months agoStep function state to execute a Glue job seems to be stalling
asked a year agoInvalid security token error when executing nested step function on Step Functions Local
Accepted Answerasked 3 months agoCan not create a stepfunction with create-state-machine command in docker-compose
asked 6 months agoStates.Runtime error when nested step function fails in Step Functions Local
asked 2 months agoUnable To create a step function
asked 5 years agoS3 object and lambda function in step machine with the asynchronous express workflows
Accepted Answerasked 7 months agoIssue with Step Function Creation
asked 2 months agoStep Function to Send Email on Error/Success
asked 7 months ago