Skip to content
This repository has been archived by the owner on Jul 20, 2022. It is now read-only.

INTERNAL_SERVER_ERROR after running aws-blog-firehose-lambda locally #31

Open
dzlab opened this issue Oct 23, 2015 · 0 comments
Open

INTERNAL_SERVER_ERROR after running aws-blog-firehose-lambda locally #31

dzlab opened this issue Oct 23, 2015 · 0 comments

Comments

@dzlab
Copy link

dzlab commented Oct 23, 2015

I tried to run the Firehose java sample locally by uncommenting lines from KinesisToFirehose.java. Here is the output:

$ mvn exec:java -Dexec.mainClass="com.amazonaws.proserv.lambda.KinesisToFirehose"
...
[INFO] --- exec-maven-plugin:1.4.0:java (default-cli) @ firehoseLambda ---
Firehose ACTIVE
deliverytest
Firehose ACTIVE
Firehose ACTIVE
{RecordId: wVgtYFcO2Pv0JlXI2cN4apw3R3mxMa9kW4GaWIXR/wUa5qVqMA14XNTLsxEpzPeP0rOO5w4EqxjoZ90NcOah6lvBkoLvqMCqsZcvazNsRtKQnUzA24BG+CPxiRJCorSPZnhCmo6+NyZch4CSB0lCLUT1/AuqKN9FBgZZ9DBg7C5vQB/BcP2VfIZAHRO69Q0XbNve2eFzEqsnzLcXcO2sue6qSf5dIOUB}
...

From the output, everything looks fine, but when I check the Firehose streams on Kinesis AWS dashboard, I see this error INTERNAL_SERVER_ERROR. Now I cannot do much of anything, I don't even see manually created firehoses and the S3 bucket is still empty.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant