awslabs / awslabs/lambda-streams-to-firehose
Error on dynamodb stream to firehose: awslabs/dynamo_continuous_backup.
- Dominant language
- JavaScript
- Stars
- 278
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
2016-11-03T16:05:24.322Z 81820a90-cb82-4566-90db-35866393c78b
{
"message": "Firehose LambdaStreamsDefaultDeliveryStream not found under account.",
"code": "ResourceNotFoundException",
"time": "2016-11-03T16:05:24.322Z",
"requestId": "54279dc9-a1df-11e6-a64e-d184623b1b33",
"statusCode": 400,
"retryable": false,
"retryDelay": 65.43006924912333
}
11/03 09:15 > grep -r LambdaStreamsDefaultDeliveryStream *
createDefaultDeliveryStream.sh:deliveryStreamName="LambdaStreamsDefaultDeliveryStream"
index.js: 'DEFAULT' : 'LambdaStreamsDefaultDeliveryStream'
Contributor guide
Research direction
Start by reading createDefaultDeliveryStream.sh and index.js, then compare how each refers to LambdaStreamsDefaultDeliveryStream. Trace the deployment or invocation path associated with the ResourceNotFoundException and verify the stream lookup succeeds under the target account; done means the DynamoDB stream-to-Firehose flow no longer reports that delivery stream as missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100