This support forum is no longer in use. Please use the Cloudinary Community at https://community.cloudinary.com/ to receive assistance from other members of the community and from Cloudinary's support team. For account-specific questions or if you believe that you've encountered a bug, please contact the Cloudinary team directly via the "submit a request" option on this support site.

"Invalid Image File"- Using GraphQL + AWS Lambda

Comments

3 comments

  • Avatar
    Stephen Doyle

    Hi Roni,

    The most likely explanation given the code above is if `stream` isn't encoded correctly, but it's hard to say for sure without seeing the full data or being able to see that request in our logs.

    Are you able to share some specific information we can use to find the request on our side? cloud name, public_id, etc?

    If you'd prefer not to share information like that here, you can also create a request for our support team directly using the form at https://support.cloudinary.com/hc/en-us/requests/new

    Regards,

    Stephen

    0
    Comment actions Permalink
  • Avatar
    Roni Yosofov

    Hi Stephen,

    Here is the information:

    Cloud name: AWS (Lambda)
    encoding: 7bit
    example public_id: post/5448522d-e373-45e3-9e93-7207052bb897

     

    What's the correct encoding for cloudinary?

    0
    Comment actions Permalink
  • Avatar
    Roni Yosofov

    ahhh i found the issue...
    I use AWS Gateway and I had to add multipart/form-data as a Binary Media Type in options... 
    Looks good now :)

     

    0
    Comment actions Permalink

Post is closed for comments.