Home

Awesome

<!-- markdownlint-disable -->

<a href="https://cpco.io/homepage"><img src="https://github.com/cloudposse-terraform-components/aws-datadog-lambda-forwarder/blob/main/.github/banner.png?raw=true" alt="Project Banner"/></a><br/> <p align="right"> <a href="https://github.com/cloudposse-terraform-components/aws-datadog-lambda-forwarder/releases/latest"><img src="https://img.shields.io/github/release/cloudposse-terraform-components/aws-datadog-lambda-forwarder.svg?style=for-the-badge" alt="Latest Release"/></a><a href="https://slack.cloudposse.com"><img src="https://slack.cloudposse.com/for-the-badge.svg" alt="Slack Community"/></a></p>

<!-- markdownlint-restore --> <!-- ** DO NOT EDIT THIS FILE ** ** This file was automatically generated by the `cloudposse/build-harness`. ** 1) Make all changes to `README.yaml` ** 2) Run `make init` (you only need to do this once) ** 3) Run`make readme` to rebuild this file. ** ** (We maintain HUNDREDS of open source projects. This is how we maintain our sanity.) ** -->

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"
<!-- prettier-ignore-start --> <!-- BEGINNING OF PRE-COMMIT-TERRAFORM DOCS HOOK -->

Requirements

NameVersion
<a name="requirement_terraform"></a> terraform>= 1.0.0
<a name="requirement_aws"></a> aws>= 4.0
<a name="requirement_datadog"></a> datadog>= 3.3.0

Providers

NameVersion
<a name="provider_datadog"></a> datadog>= 3.3.0

Modules

NameSourceVersion
<a name="module_datadog-integration"></a> datadog-integrationcloudposse/stack-config/yaml//modules/remote-state1.5.0
<a name="module_datadog_configuration"></a> datadog_configuration../datadog-configuration/modules/datadog_keysn/a
<a name="module_datadog_lambda_forwarder"></a> datadog_lambda_forwardercloudposse/datadog-lambda-forwarder/aws1.5.3
<a name="module_iam_roles"></a> iam_roles../account-map/modules/iam-rolesn/a
<a name="module_log_group_prefix"></a> log_group_prefixcloudposse/label/null0.25.0
<a name="module_this"></a> thiscloudposse/label/null0.25.0

Resources

NameType
datadog_integration_aws_lambda_arn.log_collectorresource
datadog_integration_aws_lambda_arn.rds_collectorresource
datadog_integration_aws_lambda_arn.vpc_logs_collectorresource
datadog_integration_aws_log_collection.mainresource

Inputs

NameDescriptionTypeDefaultRequired
<a name="input_additional_tag_map"></a> additional_tag_mapAdditional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id.<br/>This is for some rare cases where resources want additional configuration of tags<br/>and therefore take a list of maps with tag key, value, and additional configuration.map(string){}no
<a name="input_attributes"></a> attributesID element. Additional attributes (e.g. workers or cluster) to add to id,<br/>in the order they appear in the list. New attributes are appended to the<br/>end of the list. The elements of the list are joined by the delimiter<br/>and treated as a single ID element.list(string)[]no
<a name="input_cloudwatch_forwarder_event_patterns"></a> cloudwatch_forwarder_event_patternsMap 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<br/>Example:<pre>hcl<br/>cloudwatch_forwarder_event_rules = {<br/> "guardduty" = {<br/> source = ["aws.guardduty"]<br/> detail-type = ["GuardDuty Finding"]<br/> }<br/> "ec2-terminated" = {<br/> source = ["aws.ec2"]<br/> detail-type = ["EC2 Instance State-change Notification"]<br/> detail = {<br/> state = ["terminated"]<br/> }<br/> }<br/>}</pre><pre>map(object({<br/> version = optional(list(string))<br/> id = optional(list(string))<br/> detail-type = optional(list(string))<br/> source = optional(list(string))<br/> account = optional(list(string))<br/> time = optional(list(string))<br/> region = optional(list(string))<br/> resources = optional(list(string))<br/> detail = optional(map(list(string)))<br/> }))</pre>{}no
<a name="input_cloudwatch_forwarder_log_groups"></a> cloudwatch_forwarder_log_groupsMap 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
<a name="input_context"></a> contextSingle object for setting entire context at once.<br/>See description of individual variables for details.<br/>Leave string and numeric variables as null to use default value.<br/>Individual variable settings (non-null) override settings in context object,<br/>except for attributes, tags, and additional_tag_map, which are merged.any<pre>{<br/> "additional_tag_map": {},<br/> "attributes": [],<br/> "delimiter": null,<br/> "descriptor_formats": {},<br/> "enabled": true,<br/> "environment": null,<br/> "id_length_limit": null,<br/> "label_key_case": null,<br/> "label_order": [],<br/> "label_value_case": null,<br/> "labels_as_tags": [<br/> "unset"<br/> ],<br/> "name": null,<br/> "namespace": null,<br/> "regex_replace_chars": null,<br/> "stage": null,<br/> "tags": {},<br/> "tenant": null<br/>}</pre>no
<a name="input_context_tags"></a> context_tagsList of context tags to add to each monitorset(string)<pre>[<br/> "namespace",<br/> "tenant",<br/> "environment",<br/> "stage"<br/>]</pre>no
<a name="input_context_tags_enabled"></a> context_tags_enabledWhether to add context tags to add to each monitorbooltrueno
<a name="input_datadog_configuration_environment"></a> datadog_configuration_environmentAWS region where the Datadog configuration is deployed, useful for multi region setups, null uses default (gbl)stringnullno
<a name="input_datadog_forwarder_lambda_environment_variables"></a> datadog_forwarder_lambda_environment_variablesMap of environment variables to pass to the Lambda Functionmap(string){}no
<a name="input_dd_api_key_kms_ciphertext_blob"></a> dd_api_key_kms_ciphertext_blobCiphertextBlob stored in environment variable DD_KMS_API_KEY used by the lambda function, along with the KMS key, to decrypt Datadog API keystring""no
<a name="input_dd_artifact_filename"></a> dd_artifact_filenameThe Datadog artifact filename minus extensionstring"aws-dd-forwarder"no
<a name="input_dd_forwarder_version"></a> dd_forwarder_versionVersion tag of Datadog lambdas to use. https://github.com/DataDog/datadog-serverless-functions/releasesstring"3.66.0"no
<a name="input_dd_module_name"></a> dd_module_nameThe Datadog GitHub repository namestring"datadog-serverless-functions"no
<a name="input_dd_tags_map"></a> dd_tags_mapA map of Datadog tags to apply to all logs forwarded to Datadogmap(string){}no
<a name="input_delimiter"></a> delimiterDelimiter to be used between ID elements.<br/>Defaults to - (hyphen). Set to "" to use no delimiter at all.stringnullno
<a name="input_descriptor_formats"></a> descriptor_formatsDescribe additional descriptors to be output in the descriptors output map.<br/>Map of maps. Keys are names of descriptors. Values are maps of the form<br/>{<br/> format = string<br/> labels = list(string)<br/>}<br/>(Type is any so the map values can later be enhanced to provide additional options.)<br/>format is a Terraform format string to be passed to the format() function.<br/>labels is a list of labels, in order, to pass to format() function.<br/>Label values will be normalized before being passed to format() so they will be<br/>identical to how they appear in id.<br/>Default is {} (descriptors output will be empty).any{}no
<a name="input_enabled"></a> enabledSet to false to prevent the module from creating any resourcesboolnullno
<a name="input_environment"></a> environmentID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'stringnullno
<a name="input_forwarder_lambda_debug_enabled"></a> forwarder_lambda_debug_enabledWhether to enable or disable debug for the Lambda forwarderboolfalseno
<a name="input_forwarder_log_artifact_url"></a> forwarder_log_artifact_urlThe URL for the code of the Datadog forwarder for Logs. It can be a local file, URL or git repostringnullno
<a name="input_forwarder_log_enabled"></a> forwarder_log_enabledFlag to enable or disable Datadog log forwarderboolfalseno
<a name="input_forwarder_log_layers"></a> forwarder_log_layersList of Lambda Layer Version ARNs (maximum of 5) to attach to Datadog log forwarder lambda functionlist(string)[]no
<a name="input_forwarder_log_retention_days"></a> forwarder_log_retention_daysNumber 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]number14no
<a name="input_forwarder_rds_artifact_url"></a> forwarder_rds_artifact_urlThe URL for the code of the Datadog forwarder for RDS. It can be a local file, url or git repostringnullno
<a name="input_forwarder_rds_enabled"></a> forwarder_rds_enabledFlag to enable or disable Datadog RDS enhanced monitoring forwarderboolfalseno
<a name="input_forwarder_rds_filter_pattern"></a> forwarder_rds_filter_patternFilter pattern for Lambda forwarder RDSstring""no
<a name="input_forwarder_rds_layers"></a> forwarder_rds_layersList of Lambda Layer Version ARNs (maximum of 5) to attach to Datadog RDS enhanced monitoring lambda functionlist(string)[]no
<a name="input_forwarder_vpc_logs_artifact_url"></a> forwarder_vpc_logs_artifact_urlThe URL for the code of the Datadog forwarder for VPC Logs. It can be a local file, url or git repostringnullno
<a name="input_forwarder_vpc_logs_enabled"></a> forwarder_vpc_logs_enabledFlag to enable or disable Datadog VPC flow log forwarderboolfalseno
<a name="input_forwarder_vpc_logs_layers"></a> forwarder_vpc_logs_layersList of Lambda Layer Version ARNs (maximum of 5) to attach to Datadog VPC flow log forwarder lambda functionlist(string)[]no
<a name="input_forwarder_vpclogs_filter_pattern"></a> forwarder_vpclogs_filter_patternFilter pattern for Lambda forwarder VPC Logsstring""no
<a name="input_id_length_limit"></a> id_length_limitLimit id to this many characters (minimum 6).<br/>Set to 0 for unlimited length.<br/>Set to null for keep the existing setting, which defaults to 0.<br/>Does not affect id_full.numbernullno
<a name="input_kms_key_id"></a> kms_key_idOptional KMS key ID to encrypt Datadog Lambda function logsstringnullno
<a name="input_label_key_case"></a> label_key_caseControls the letter case of the tags keys (label names) for tags generated by this module.<br/>Does not affect keys of tags passed in via the tags input.<br/>Possible values: lower, title, upper.<br/>Default value: title.stringnullno
<a name="input_label_order"></a> label_orderThe order in which the labels (ID elements) appear in the id.<br/>Defaults to ["namespace", "environment", "stage", "name", "attributes"].<br/>You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.list(string)nullno
<a name="input_label_value_case"></a> label_value_caseControls the letter case of ID elements (labels) as included in id,<br/>set as tag values, and output by this module individually.<br/>Does not affect values of tags passed in via the tags input.<br/>Possible values: lower, title, upper and none (no transformation).<br/>Set this to title and set delimiter to "" to yield Pascal Case IDs.<br/>Default value: lower.stringnullno
<a name="input_labels_as_tags"></a> labels_as_tagsSet of labels (ID elements) to include as tags in the tags output.<br/>Default is to include all labels.<br/>Tags with empty values will not be included in the tags output.<br/>Set to [] to suppress all generated tags.<br/>Notes:<br/> The value of the name tag, if included, will be the id, not the name.<br/> Unlike other null-label inputs, the initial setting of labels_as_tags cannot be<br/> changed in later chained modules. Attempts to change it will be silently ignored.set(string)<pre>[<br/> "default"<br/>]</pre>no
<a name="input_lambda_arn_enabled"></a> lambda_arn_enabledEnable adding the Lambda Arn to this account integrationbooltrueno
<a name="input_lambda_policy_source_json"></a> lambda_policy_source_jsonAdditional IAM policy document that can optionally be passed and merged with the created policy documentstring""no
<a name="input_lambda_reserved_concurrent_executions"></a> lambda_reserved_concurrent_executionsAmount 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 -1number-1no
<a name="input_lambda_runtime"></a> lambda_runtimeRuntime environment for Datadog Lambdastring"python3.8"no
<a name="input_log_collection_services"></a> log_collection_servicesList of log collection services to enablelist(string)<pre>[<br/> "apigw-access-logs",<br/> "apigw-execution-logs",<br/> "elbv2",<br/> "elb",<br/> "cloudfront",<br/> "lambda",<br/> "redshift",<br/> "s3"<br/>]</pre>no
<a name="input_name"></a> nameID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.<br/>This is the only ID element not also included as a tag.<br/>The "name" tag is set to the full id string. There is no tag with the value of the name input.stringnullno
<a name="input_namespace"></a> namespaceID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally uniquestringnullno
<a name="input_regex_replace_chars"></a> regex_replace_charsTerraform regular expression (regex) string.<br/>Characters matching the regex will be removed from the ID elements.<br/>If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.stringnullno
<a name="input_region"></a> regionAWS Regionstringn/ayes
<a name="input_s3_bucket_kms_arns"></a> s3_bucket_kms_arnsList of KMS key ARNs for s3 bucket encryptionlist(string)[]no
<a name="input_s3_buckets"></a> s3_bucketsThe names of S3 buckets to forward logs to Datadoglist(string)[]no
<a name="input_s3_buckets_with_prefixes"></a> s3_buckets_with_prefixesThe names S3 buckets and prefix to forward logs to Datadogmap(object({ bucket_name : string, bucket_prefix : string })){}no
<a name="input_security_group_ids"></a> security_group_idsList of security group IDs to use when the Lambda Function runs in a VPClist(string)nullno
<a name="input_stage"></a> stageID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'stringnullno
<a name="input_subnet_ids"></a> subnet_idsList of subnet IDs to use when deploying the Lambda Function in a VPClist(string)nullno
<a name="input_tags"></a> tagsAdditional tags (e.g. {'BusinessUnit': 'XYZ'}).<br/>Neither the tag keys nor the tag values will be modified by this module.map(string){}no
<a name="input_tenant"></a> tenantID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is forstringnullno
<a name="input_tracing_config_mode"></a> tracing_config_modeCan 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 servicestring"PassThrough"no
<a name="input_vpclogs_cloudwatch_log_group"></a> vpclogs_cloudwatch_log_groupThe name of the CloudWatch Log Group for VPC flow logsstringnullno

Outputs

NameDescription
<a name="output_lambda_forwarder_log_function_arn"></a> lambda_forwarder_log_function_arnDatadog Lambda forwarder CloudWatch/S3 function ARN
<a name="output_lambda_forwarder_log_function_name"></a> lambda_forwarder_log_function_nameDatadog Lambda forwarder CloudWatch/S3 function name
<a name="output_lambda_forwarder_rds_enhanced_monitoring_function_name"></a> lambda_forwarder_rds_enhanced_monitoring_function_nameDatadog Lambda forwarder RDS Enhanced Monitoring function name
<a name="output_lambda_forwarder_rds_function_arn"></a> lambda_forwarder_rds_function_arnDatadog Lambda forwarder RDS Enhanced Monitoring function ARN
<a name="output_lambda_forwarder_vpc_log_function_arn"></a> lambda_forwarder_vpc_log_function_arnDatadog Lambda forwarder VPC Flow Logs function ARN
<a name="output_lambda_forwarder_vpc_log_function_name"></a> lambda_forwarder_vpc_log_function_nameDatadog Lambda forwarder VPC Flow Logs function name
<!-- END OF PRE-COMMIT-TERRAFORM DOCS HOOK --> <!-- prettier-ignore-end -->

References

[!TIP]

πŸ‘½ Use Atmos with Terraform

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

<details> <summary><strong>Watch demo of using Atmos with Terraform</strong></summary> <img src="https://github.com/cloudposse/atmos/blob/main/docs/demo.gif?raw=true"/><br/> <i>Example of running <a href="https://atmos.tools"><code>atmos</code></a> to manage infrastructure from our <a href="https://atmos.tools/quick-start/">Quick Start</a> tutorial.</i> </detalis>

Related Projects

Check out these related projects.

[!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.<br/> βœ… Your team owns everything.<br/> βœ… 100% Open Source and backed by fanatical support.<br/>

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-datadog-lambda-forwarder&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>

<details><summary>πŸ“š <strong>Learn More</strong></summary> <br/>

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

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-datadog-lambda-forwarder&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>

Day-2: Your Operational Mastery

<a href="https://cpco.io/commercial-support?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-datadog-lambda-forwarder&utm_content=commercial_support"><img alt="Request Quote" src="https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge"/></a>

</details>

✨ Contributing

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

Many thanks to our outstanding contributors:

<a href="https://github.com/cloudposse-terraform-components/aws-datadog-lambda-forwarder/graphs/contributors"> <img src="https://contrib.rocks/image?repo=cloudposse-terraform-components/aws-datadog-lambda-forwarder&max=24" /> </a>

For πŸ› bug reports & feature requests, please use the issue tracker.

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

  1. Review our Code of Conduct and Contributor Guidelines.
  2. Fork the repo on GitHub
  3. Clone the project to your own machine
  4. Commit changes to your own branch
  5. Push your work back up to your fork
  6. 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 <a href="https://cloudposse.com/office-hours?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-datadog-lambda-forwarder&utm_content=office_hours"><img src="https://img.cloudposse.com/fit-in/200x200/https://cloudposse.com/wp-content/uploads/2019/08/Powered-by-Zoom.png" align="right" /></a>

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

<a href="https://opensource.org/licenses/Apache-2.0"><img src="https://img.shields.io/badge/License-Apache%202.0-blue.svg?style=for-the-badge" alt="License"></a>

<details> <summary>Preamble to the Apache License, Version 2.0</summary> <br/> <br/>
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.
</details>

Trademarks

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


Copyright Β© 2017-2024 Cloud Posse, LLC

<a href="https://cloudposse.com/readme/footer/link?utm_source=github&utm_medium=readme&utm_campaign=cloudposse-terraform-components/aws-datadog-lambda-forwarder&utm_content=readme_footer_link"><img alt="README footer" src="https://cloudposse.com/readme/footer/img"/></a>

<img alt="Beacon" width="0" src="https://ga-beacon.cloudposse.com/UA-76589703-4/cloudposse-terraform-components/aws-datadog-lambda-forwarder?pixel&cs=github&cm=readme&an=aws-datadog-lambda-forwarder"/>