Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws-kinesisfirehose-destinations: add datadog destination in cdk similar to console #20354

Open
2 tasks
aayushchhabra1999 opened this issue May 15, 2022 · 1 comment · May be fixed by #33657
Open
2 tasks

aws-kinesisfirehose-destinations: add datadog destination in cdk similar to console #20354

aayushchhabra1999 opened this issue May 15, 2022 · 1 comment · May be fixed by #33657
Labels
@aws-cdk/aws-kinesisfirehose Related to Amazon Kinesis Data Firehose effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p3

Comments

@aayushchhabra1999
Copy link

aayushchhabra1999 commented May 15, 2022

Describe the feature

Requesting addition of datadog destination to the aws-kinesisfirehose-destinations package.
Currently, the console supports third party destinations natively but they are not supported programmatically.
image

Use Case

We use an analytics stack and it causes frustration to create a delivery stream every time we take down and redeploy the stack. The only way we have at the moment is using console and that introduces manual effort. If there is a destination for datadog (similar to s3 that currently exists), we'd be able to automate the complete flow with cdk deploy.

Proposed Solution

No response

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

CDK version used

v2

Environment details (OS name and version, etc.)

N/A

@aayushchhabra1999 aayushchhabra1999 added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels May 15, 2022
@github-actions github-actions bot added the @aws-cdk/aws-kinesisfirehose Related to Amazon Kinesis Data Firehose label May 15, 2022
@aayushchhabra1999 aayushchhabra1999 changed the title aws-kinesisfirehose-destinations: datadog destination aws-kinesisfirehose-destinations: native datadog destination in cdk similar to console May 15, 2022
@aayushchhabra1999 aayushchhabra1999 changed the title aws-kinesisfirehose-destinations: native datadog destination in cdk similar to console aws-kinesisfirehose-destinations: datadog destination in cdk similar to console May 15, 2022
@aayushchhabra1999 aayushchhabra1999 changed the title aws-kinesisfirehose-destinations: datadog destination in cdk similar to console aws-kinesisfirehose-destinations: add datadog destination in cdk similar to console May 15, 2022
@otaviomacedo otaviomacedo added p2 effort/medium Medium work item – several days of effort and removed needs-triage This issue or PR still needs to be triaged. labels Jun 29, 2022
@otaviomacedo otaviomacedo removed their assignment Jun 29, 2022
@ansraliant
Copy link

@aayushchhabra1999 CloudFormation still does not have a Datadog destination like in the AWS Console. But that does not mean that it doesn't work.
Datadog is just a HTTPDestination. So all you have to do for it to work with CDK is set it up.
Remember to add the correct URL for datadog depending on the region of your datadog. This URL is not that well documented, and there are multiple choices, the one that works should be in the format of https://aws-kinesis-http-intake.logs.datadoghq.com/v1/input
The API KEY you can put it on the access_key field and it works.
I have Datadog as a destination for kinesis working and managed by CDK.

@pahud pahud added p3 and removed p2 labels Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-kinesisfirehose Related to Amazon Kinesis Data Firehose effort/medium Medium work item – several days of effort feature-request A feature should be added or improved. p3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants