GitHub - cloudposse-terraform-components/aws-datadog-lambda-forwarder: This component is responsible for provision all the necessary infrastructure to deploy Datadog Lambda forwarders

This component is responsible for provision all the necessary infrastructure to deploy Datadog Lambda forwarders. It depends on the datadog-configuration component to get the Datadog API keys.

Usage

Stack Level: Regional

Here's an example snippet for how to use this component:

components:
  terraform:
    datadog-lambda-forwarder:
      settings:
        spacelift:
          workspace_enabled: true
      vars:
        enabled: true
        name: datadog-lambda-forwarder
        # Set `forwarder_rds_enabled`  to `true` and configure `rds-enhanced-monitoring` Log Group when:
        # 1. The account has RDS instances provisioned
        # 2. RDS Enhanced Monitoring is enabled
        # 3. CloudWatch Log Group `RDSOSMetrics` exists (it will be created by AWS automatically when RDS Enhanced Monitoring is enabled)
        forwarder_rds_enabled: true
        forwarder_log_enabled: true
        forwarder_vpc_logs_enabled: true
        cloudwatch_forwarder_log_groups:
          rds-enhanced-monitoring:
            name: "RDSOSMetrics"
            filter_pattern: ""
          eks-cluster:
            # Use either `name` or `name_prefix` with `name_suffix`
            # If `name_prefix` with `name_suffix` are used, the final `name` will be constructed using `name_prefix` + context + `name_suffix`,
            # e.g. "/aws/eks/eg-ue2-prod-eks-cluster/cluster"
            name_prefix: "/aws/eks/"
            name_suffix: "eks-cluster/cluster"
            filter_pattern: ""
          transfer-sftp:
            name: "/aws/transfer/s-xxxxxxxxxxxx"
            filter_pattern: ""

Note for other regions, you need to deploy the datadog-configuration component in the respective region - the datadog configuration will be moving to a regional implementation.

For example if you usually deploy to us-west-2 (and DD Configuration is gbl), deploy it to the new region and then deploy the lambda forwarder.

import:
  - orgs/acme/plat/dev/_defaults
  - mixins/region/us-east-1
  - catalog/datadog/configuration
  - catalog/datadog/lambda-forwarder

components:
  terraform:
    datadog-configuration:
      vars:
        datadog_secrets_store_type: SSM
        datadog_secrets_source_store_account_stage: auto
        datadog_secrets_source_store_account_region: "us-west-2"

    datadog-lambda-forwarder:
      vars:
        datadog_configuration_environment: "use1"

Requirements

Name	Version
terraform	>= 1.0.0
aws	>= 4.0
datadog	>= 3.3.0

Providers

Name	Version
datadog	>= 3.3.0

Modules

Name	Source	Version
datadog-integration	cloudposse/stack-config/yaml//modules/remote-state	1.5.0
datadog_configuration	../datadog-configuration/modules/datadog_keys	n/a
datadog_lambda_forwarder	cloudposse/datadog-lambda-forwarder/aws	1.5.3
iam_roles	../account-map/modules/iam-roles	n/a
log_group_prefix	cloudposse/label/null	0.25.0
this	cloudposse/label/null	0.25.0

Resources

Name	Type
datadog_integration_aws_lambda_arn.log_collector	resource
datadog_integration_aws_lambda_arn.rds_collector	resource
datadog_integration_aws_lambda_arn.vpc_logs_collector	resource
datadog_integration_aws_log_collection.main	resource

Inputs

Name	Description	Type	Default	Required
additional_tag_map	Additional key-value pairs to add to each map in `tags_as_list_of_maps`. Not added to `tags` or `id`. This is for some rare cases where resources want additional configuration of tags and therefore take a list of maps with tag key, value, and additional configuration.	`map(string)`	`{}`	no
attributes	ID element. Additional attributes (e.g. `workers` or `cluster`) to add to `id`, in the order they appear in the list. New attributes are appended to the end of the list. The elements of the list are joined by the `delimiter` and treated as a single ID element.	`list(string)`	`[]`	no
cloudwatch_forwarder_event_patterns	Map of title to CloudWatch Event patterns to forward to Datadog. Event structure from here: https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/CloudWatchEventsandEventPatterns.html#CloudWatchEventsPatterns Example: hcl cloudwatch_forwarder_event_rules = { "guardduty" = { source = ["aws.guardduty"] detail-type = ["GuardDuty Finding"] } "ec2-terminated" = { source = ["aws.ec2"] detail-type = ["EC2 Instance State-change Notification"] detail = { state = ["terminated"] } } }	map(object({ version = optional(list(string)) id = optional(list(string)) detail-type = optional(list(string)) source = optional(list(string)) account = optional(list(string)) time = optional(list(string)) region = optional(list(string)) resources = optional(list(string)) detail = optional(map(list(string))) }))	`{}`	no
cloudwatch_forwarder_log_groups	Map of CloudWatch Log Groups with a filter pattern that the Lambda forwarder will send logs from. For example: { mysql1 = { name = "/aws/rds/maincluster", filter_pattern = "" }	`map(map(string))`	`{}`	no
context	Single object for setting entire context at once. See description of individual variables for details. Leave string and numeric variables as `null` to use default value. Individual variable settings (non-null) override settings in context object, except for attributes, tags, and additional_tag_map, which are merged.	`any`	{ "additional_tag_map": {}, "attributes": [], "delimiter": null, "descriptor_formats": {}, "enabled": true, "environment": null, "id_length_limit": null, "label_key_case": null, "label_order": [], "label_value_case": null, "labels_as_tags": [ "unset" ], "name": null, "namespace": null, "regex_replace_chars": null, "stage": null, "tags": {}, "tenant": null }	no
context_tags	List of context tags to add to each monitor	`set(string)`	[ "namespace", "tenant", "environment", "stage" ]	no
context_tags_enabled	Whether to add context tags to add to each monitor	`bool`	`true`	no
datadog_configuration_environment	AWS region where the Datadog configuration is deployed, useful for multi region setups, null uses default (gbl)	`string`	`null`	no
datadog_forwarder_lambda_environment_variables	Map of environment variables to pass to the Lambda Function	`map(string)`	`{}`	no
dd_api_key_kms_ciphertext_blob	CiphertextBlob stored in environment variable DD_KMS_API_KEY used by the lambda function, along with the KMS key, to decrypt Datadog API key	`string`	`""`	no
dd_artifact_filename	The Datadog artifact filename minus extension	`string`	`"aws-dd-forwarder"`	no
dd_forwarder_version	Version tag of Datadog lambdas to use. https://github.com/DataDog/datadog-serverless-functions/releases	`string`	`"3.66.0"`	no
dd_module_name	The Datadog GitHub repository name	`string`	`"datadog-serverless-functions"`	no
dd_tags_map	A map of Datadog tags to apply to all logs forwarded to Datadog	`map(string)`	`{}`	no
delimiter	Delimiter to be used between ID elements. Defaults to `-` (hyphen). Set to `""` to use no delimiter at all.	`string`	`null`	no
descriptor_formats	Describe additional descriptors to be output in the `descriptors` output map. Map of maps. Keys are names of descriptors. Values are maps of the form `{<br/> format = string<br/> labels = list(string)<br/>}` (Type is `any` so the map values can later be enhanced to provide additional options.) `format` is a Terraform format string to be passed to the `format()` function. `labels` is a list of labels, in order, to pass to `format()` function. Label values will be normalized before being passed to `format()` so they will be identical to how they appear in `id`. Default is `{}` (`descriptors` output will be empty).	`any`	`{}`	no
enabled	Set to false to prevent the module from creating any resources	`bool`	`null`	no
environment	ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'	`string`	`null`	no
forwarder_lambda_debug_enabled	Whether to enable or disable debug for the Lambda forwarder	`bool`	`false`	no
forwarder_log_artifact_url	The URL for the code of the Datadog forwarder for Logs. It can be a local file, URL or git repo	`string`	`null`	no
forwarder_log_enabled	Flag to enable or disable Datadog log forwarder	`bool`	`false`	no
forwarder_log_layers	List of Lambda Layer Version ARNs (maximum of 5) to attach to Datadog log forwarder lambda function	`list(string)`	`[]`	no
forwarder_log_retention_days	Number of days to retain Datadog forwarder lambda execution logs. One of [0 1 3 5 7 14 30 60 90 120 150 180 365 400 545 731 1827 3653]	`number`	`14`	no
forwarder_rds_artifact_url	The URL for the code of the Datadog forwarder for RDS. It can be a local file, url or git repo	`string`	`null`	no
forwarder_rds_enabled	Flag to enable or disable Datadog RDS enhanced monitoring forwarder	`bool`	`false`	no
forwarder_rds_filter_pattern	Filter pattern for Lambda forwarder RDS	`string`	`""`	no
forwarder_rds_layers	List of Lambda Layer Version ARNs (maximum of 5) to attach to Datadog RDS enhanced monitoring lambda function	`list(string)`	`[]`	no
forwarder_vpc_logs_artifact_url	The URL for the code of the Datadog forwarder for VPC Logs. It can be a local file, url or git repo	`string`	`null`	no
forwarder_vpc_logs_enabled	Flag to enable or disable Datadog VPC flow log forwarder	`bool`	`false`	no
forwarder_vpc_logs_layers	List of Lambda Layer Version ARNs (maximum of 5) to attach to Datadog VPC flow log forwarder lambda function	`list(string)`	`[]`	no
forwarder_vpclogs_filter_pattern	Filter pattern for Lambda forwarder VPC Logs	`string`	`""`	no
id_length_limit	Limit `id` to this many characters (minimum 6). Set to `0` for unlimited length. Set to `null` for keep the existing setting, which defaults to `0`. Does not affect `id_full`.	`number`	`null`	no
kms_key_id	Optional KMS key ID to encrypt Datadog Lambda function logs	`string`	`null`	no
label_key_case	Controls the letter case of the `tags` keys (label names) for tags generated by this module. Does not affect keys of tags passed in via the `tags` input. Possible values: `lower`, `title`, `upper`. Default value: `title`.	`string`	`null`	no
label_order	The order in which the labels (ID elements) appear in the `id`. Defaults to ["namespace", "environment", "stage", "name", "attributes"]. You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.	`list(string)`	`null`	no
label_value_case	Controls the letter case of ID elements (labels) as included in `id`, set as tag values, and output by this module individually. Does not affect values of tags passed in via the `tags` input. Possible values: `lower`, `title`, `upper` and `none` (no transformation). Set this to `title` and set `delimiter` to `""` to yield Pascal Case IDs. Default value: `lower`.	`string`	`null`	no
labels_as_tags	Set of labels (ID elements) to include as tags in the `tags` output. Default is to include all labels. Tags with empty values will not be included in the `tags` output. Set to `[]` to suppress all generated tags. Notes: The value of the `name` tag, if included, will be the `id`, not the `name`. Unlike other `null-label` inputs, the initial setting of `labels_as_tags` cannot be changed in later chained modules. Attempts to change it will be silently ignored.	`set(string)`	[ "default" ]	no
lambda_arn_enabled	Enable adding the Lambda Arn to this account integration	`bool`	`true`	no
lambda_policy_source_json	Additional IAM policy document that can optionally be passed and merged with the created policy document	`string`	`""`	no
lambda_reserved_concurrent_executions	Amount of reserved concurrent executions for the lambda function. A value of 0 disables Lambda from being triggered and -1 removes any concurrency limitations. Defaults to Unreserved Concurrency Limits -1	`number`	`-1`	no
lambda_runtime	Runtime environment for Datadog Lambda	`string`	`"python3.8"`	no
log_collection_services	List of log collection services to enable	`list(string)`	[ "apigw-access-logs", "apigw-execution-logs", "elbv2", "elb", "cloudfront", "lambda", "redshift", "s3" ]	no
name	ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'. This is the only ID element not also included as a `tag`. The "name" tag is set to the full `id` string. There is no tag with the value of the `name` input.	`string`	`null`	no
namespace	ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique	`string`	`null`	no
regex_replace_chars	Terraform regular expression (regex) string. Characters matching the regex will be removed from the ID elements. If not set, `"/[^a-zA-Z0-9-]/"` is used to remove all characters other than hyphens, letters and digits.	`string`	`null`	no
region	AWS Region	`string`	n/a	yes
s3_bucket_kms_arns	List of KMS key ARNs for s3 bucket encryption	`list(string)`	`[]`	no
s3_buckets	The names of S3 buckets to forward logs to Datadog	`list(string)`	`[]`	no
s3_buckets_with_prefixes	The names S3 buckets and prefix to forward logs to Datadog	`map(object({ bucket_name : string, bucket_prefix : string }))`	`{}`	no
security_group_ids	List of security group IDs to use when the Lambda Function runs in a VPC	`list(string)`	`null`	no
stage	ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'	`string`	`null`	no
subnet_ids	List of subnet IDs to use when deploying the Lambda Function in a VPC	`list(string)`	`null`	no
tags	Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`). Neither the tag keys nor the tag values will be modified by this module.	`map(string)`	`{}`	no
tenant	ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for	`string`	`null`	no
tracing_config_mode	Can be either PassThrough or Active. If PassThrough, Lambda will only trace the request from an upstream service if it contains a tracing header with 'sampled=1'. If Active, Lambda will respect any tracing header it receives from an upstream service	`string`	`"PassThrough"`	no
vpclogs_cloudwatch_log_group	The name of the CloudWatch Log Group for VPC flow logs	`string`	`null`	no

Outputs

Name	Description
lambda_forwarder_log_function_arn	Datadog Lambda forwarder CloudWatch/S3 function ARN
lambda_forwarder_log_function_name	Datadog Lambda forwarder CloudWatch/S3 function name
lambda_forwarder_rds_enhanced_monitoring_function_name	Datadog Lambda forwarder RDS Enhanced Monitoring function name
lambda_forwarder_rds_function_arn	Datadog Lambda forwarder RDS Enhanced Monitoring function ARN
lambda_forwarder_vpc_log_function_arn	Datadog Lambda forwarder VPC Flow Logs function ARN
lambda_forwarder_vpc_log_function_name	Datadog Lambda forwarder VPC Flow Logs function name

References

Datadog's documentation about provisioning keys
cloudposse/terraform-aws-components - Cloud Posse's upstream component

Tip

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform.
Works with Github Actions, Atlantis, or Spacelift.

Watch demo of using Atmos with Terraform

Example of running atmos to manage infrastructure from our Quick Start tutorial.

Related Projects

Check out these related projects.

Cloud Posse Terraform Modules - Our collection of reusable Terraform modules used by our reference architectures.
Atmos - Atmos is like docker-compose but for your infrastructure

Tip

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

✅ We build it together with your team.
✅ Your team owns everything.
✅ 100% Open Source and backed by fanatical support.

📚 Learn More

Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

Day-2: Your Operational Mastery

Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

Review our Code of Conduct and Contributor Guidelines.
Fork the repo on GitHub
Clone the project to your own machine
Commit changes to your own branch
Push your work back up to your fork
Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

Preamble to the Apache License, Version 2.0

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

Name		Name	Last commit message	Last commit date
Latest commit History 31 Commits
.github		.github
docs		docs
src		src
test		test
.editorconfig		.editorconfig
.gitattributes		.gitattributes
.gitignore		.gitignore
.pre-commit-config.yaml		.pre-commit-config.yaml
.tflint.hcl		.tflint.hcl
Makefile		Makefile
README.md		README.md
README.yaml		README.yaml
_typos.toml		_typos.toml

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Usage

Requirements

Providers

Modules

Resources

Inputs

Outputs

References

👽 Use Atmos with Terraform

Related Projects

Use Terraform Reference Architectures for AWS

Day-0: Your Foundation for Success

Day-2: Your Operational Mastery

✨ Contributing

🌎 Slack Community

📰 Newsletter

📆 Office Hours

License

Trademarks

About

Releases 4

Sponsor this project

Packages

Contributors 15

Languages

cloudposse-terraform-components/aws-datadog-lambda-forwarder

Folders and files

Latest commit

History

Repository files navigation

Usage

Requirements

Providers

Modules

Resources

Inputs

Outputs

References

👽 Use Atmos with Terraform

Related Projects

Use Terraform Reference Architectures for AWS

Day-0: Your Foundation for Success

Day-2: Your Operational Mastery

✨ Contributing

🌎 Slack Community

📰 Newsletter

📆 Office Hours

License

Trademarks

About

Topics

Resources

Code of conduct

Security policy

Stars

Watchers

Forks

Releases 4

Sponsor this project

Packages 0

Contributors 15

Languages

Packages