(aws-kinesisfirehose): Custom Http Endpoint destinations for DeliveryStream
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 71
Description
Allow users to specify any custom Http endpoint as the destination for their `DeliveryStream`. This will also include 3rd party destinations, i.e. Splunk.
Part of https://github.com/aws/aws-cdk/issues/7536
### Use Case
This feature is needed for users who want to use Kinesis Data Firehose delivery streams with a non-AWS destination.
### Proposed Solution
See [RFC 340: Kinesis Firehose Delivery Stream](https://github.com/aws/aws-cdk-rfcs/pull/342)
And [this branch with the prototype](https://github.com/madeline-k/aws-cdk/tree/madeline-k/feat/kinesisfirehose-l2)
* [ ] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change
---
This is a :rocket: Feature Request
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading RFC 340, “Kinesis Firehose Delivery Stream,” and reviewing the prototype on the linked branch. Trace how the proposed L2 support should expose custom HTTP endpoint destinations, including third-party destinations such as Splunk; done means the feature is implemented consistently with the RFC and validated by the relevant project checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100