Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by
Title
g
gifted-terabyte-92288
01/08/2021, 4:12 PM
Morning! Question about the DataDog provider: Is this method:
https://www.pulumi.com/docs/reference/pkg/datadog/aws/integrationlogcollection/
the same thing as setting this up manually?
https://docs.datadoghq.com/logs/guide/send-aws-services-logs-with-the-datadog-lambda-function/?tab=awsconsole
w
witty-candle-66007
01/08/2021, 5:11 PM
It should be, yes. Essentially it addresses the last step of the manual steps where you identify the service triggers. The lambda forwarder could be created using the Pulumi lambda module:
https://www.pulumi.com/docs/reference/pkg/aws/lambda/
Or if totally adhering to the Datadog guide, use the cloudformation module:
https://www.pulumi.com/docs/reference/pkg/aws/cloudformation/
g
gifted-terabyte-92288
01/08/2021, 5:24 PM
Excellent! Thank you,
@witty-candle-66007
!
#aws
Join Slack