Going to screenshare with the #AWS support later about this, this shows me that
the bug I am trying to pinpoint is not a simple fix on my end. Just computers,
being computers. /status/1319617362337910785
2 replies
Replying to @coderbyheart
Replying to @coderbyheart
Option 1 (add $default route) did not improve the situation.
Now I am adding an additional route to the HTTP API after CloudFormation/CDK is
finished deploying:
https://github.com/bifravst/aws/commit/ff04fbb19a0a8edf9c6c1efc78da34aa2278ff18
... looks promising so far.