Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
p
purple-application-23904
12/06/2021, 9:18 PMAnyone have experience with AWS websockets? I'm trying to follow their demo but using Pulumi and I'm running into an issue:
Single character "payload" works fine and gets routed properly to my Lambda; however, multi-character payloads return a 500 error and don't appear to make it to my lambda function. I'm not sure if I'm not translating it properly from serverless template.yaml or not.
I'll thread a few images and snippets to help demonstrate / explain.
Here's the relevant part of the Pulumi code
Here's from the gateway logs for that requestId. There's no corresponding messages on the lambda handler logs.
Hey, just bumping this to see if anyone's got experience with AWS websockets that might know what's going on here - why multi-character messages are getting an error from the API gateway.