Open aayushchhabra1999 opened 2 years ago
@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.
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.
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
CDK version used
v2
Environment details (OS name and version, etc.)
N/A