1 Answer
- Newest
- Most votes
- Most comments
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 2 years ago
Relevant content
- Accepted Answerasked 7 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago