- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Sorry you ran into this trouble. Step Functions needs the response from that API call to be serializable as JSON. State payload (what's passed between states in your State Machine) If you have a file in S3 that contains such data, you will get that back in the response payload and it will be used (after output processing) as state output from that Task. In this case, your file is a binary .wav file can't. See the link below for more on the State Machine data in the Developer Guide for Step Functions: https://docs.aws.amazon.com/step-functions/latest/dg/concepts-state-machine-data.html
Given this, I'm curious what you were looking to accomplish with your workflow that involved the .wav file? Builders often use Step Functions to manage such data, but do it using "pointers" (i.e. S3 keys) in their workflow rather than loading data into the workflow state.
- Is there a way I can retrieve the binary .wav encoded in a format that is serializable as text such as base64 or UTF-8?
- What I am trying to do is build a serverless, codeless solution that sends an email with the body from one file an S3 bucket with a wav file (which can be very large) from another S3 bucket attached. I see the following challenges: a. The SendEmail Action in the SES V2 API does not accept S3 keys as input. b. The SendEmail Action in the SES V2 does not provide an easy way to add an attachment. The only way is to manually build a properly formatted and encoded MIME message. c. There is no AWS service that I can find that codelessly handles building and encoding MIME messages. d. The size of some of the WAV file attachments exceed the 262,144 byte maximum input/output size of a step function task.
- What is your advice about addressing the challenges?
- Is my only option to use Lambda and forget about it being codeless?
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa