/terraform-aws-datadog-integration

Terraform Module for integration DataDog with AWS

Primary LanguageHCLApache License 2.0Apache-2.0

README Header

Cloud Posse

terraform-aws-datadog-integration Build Status Latest Release Slack Community

Terraform Module for integration DataDog with AWS


This project is part of our comprehensive "SweetOps" approach towards DevOps.

Terraform Open Source Modules

It's 100% Open Source and licensed under the APACHE2.

We literally have hundreds of terraform modules that are Open Source and well-maintained. Check them out!

Usage

Note: At the moment this module supports a limited set of IAM policies to support Datadog integrations. More can be added as needed.

Structure

This module follows Datadog's documentation by supporting a core integration which is the minimum set of permissions needed for any Datadog integration, plus an additional integration per service which contains the additional permissions Datadog has documented are required for that service.

To make things easier, this module also implements an all integration which includes all the permissions Datadog lists under "All Permissions" as the maximal set of permissions required, so you can just set integrations = ["all"] and be done.

Note: For legacy reasons, the RDS policy is retained to be a stand-alone policy for supporting Datadog's RDS integration. It is not a good example to follow. Use Lambda as your example for adding more integrations.

Installation

For security, Datadog uses an AWS External ID when assuming the role this module creates. To configure this:

  1. Go to Datadog's integration control panel and begin the integration process by adding an account, at which point Datadog will generate the AWS External ID.
  2. Set the Terraform variable datadog_external_id to the AWS External ID as a string.
  3. Apply the Terraform plan to create the role, and note the name of the role created.
  4. Enter the name of the created role in Datadog's integration control panel where it says "AWS Role name:".

Include this module in your existing terraform code:

module "datadog_aws_integration" {
  source = "git::https://github.com/cloudposse/terraform-datadog-aws-integration.git?ref=master"
  namespace                  = "${var.namespace}"
  name                       = "${var.name}"
  stage                      = "${var.stage}"
  datadog_external_id        = "dfae1fe3434..."
  integrations               = ["core", "Lambda", ...]
}

Makefile Targets

Available targets:

  help                                Help screen
  help/all                            Display help for all targets
  help/short                          This help short screen
  lint                                Lint terraform code

Inputs

Name Description Type Default Required
attributes Additional attributes (e.g. 1) list <list> no
datadog_aws_account_id The AWS account ID Datadog's integration servers use for all integrations string 464622532012 no
datadog_external_id AWS External ID for this Datadog integration string - yes
integrations List of AWS permission names to apply for different integrations (all, core, rds) list - yes
name The Name of the application or solution (e.g. bastion or portal) string datadog no
namespace Namespace (e.g. cp or cloudposse) string - yes
stage Stage (e.g. prod, dev, staging) string - yes

Outputs

Name Description
role Name of the AWS IAM Role for Datadog to use for this integration

Share the Love

Like this project? Please give it a ★ on our GitHub! (it helps us a lot)

Are you using this project or any of our other projects? Consider leaving a testimonial. =)

Related Projects

Check out these related projects.

  • fluentd-datadog-logs - Dockerfile that implements fluentd log forwarding to datadog's new log service
  • terraform-datadog-monitor - Terraform module to provision Standard System Monitors (cpu, memory, swap, io, etc) in Datadog

Help

Got a question?

File a GitHub issue, send us an email or join our Slack Community.

README Commercial Support

Commercial Support

Work directly with our team of DevOps experts via email, slack, and video conferencing.

We provide commercial support for all of our Open Source projects. As a Dedicated Support customer, you have access to our team of subject matter experts at a fraction of the cost of a full-time engineer.

E-Mail

  • Questions. We'll use a Shared Slack channel between your team and ours.
  • Troubleshooting. We'll help you triage why things aren't working.
  • Code Reviews. We'll review your Pull Requests and provide constructive feedback.
  • Bug Fixes. We'll rapidly work to fix any bugs in our projects.
  • Build New Terraform Modules. We'll develop original modules to provision infrastructure.
  • Cloud Architecture. We'll assist with your cloud strategy and design.
  • Implementation. We'll provide hands-on support to implement our reference architectures.

Terraform Module Development

Are you interested in custom Terraform module development? Submit your inquiry using our form today and we'll get back to you ASAP.

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

Signup for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.

Contributing

Bug Reports & Feature Requests

Please use the issue tracker to report any bugs or file feature requests.

Developing

If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.

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

  1. Fork the repo on GitHub
  2. Clone the project to your own machine
  3. Commit changes to your own branch
  4. Push your work back up to your fork
  5. 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!

Copyright

Copyright © 2017-2019 Cloud Posse, LLC

License

License

See LICENSE for full details.

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.

About

This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know by leaving a testimonial!

Cloud Posse

We're a DevOps Professional Services company based in Los Angeles, CA. We ❤️ Open Source Software.

We offer paid support on all of our projects.

Check out our other projects, follow us on twitter, apply for a job, or hire us to help with your cloud strategy and implementation.

Contributors

Sergey Vasilyev
Sergey Vasilyev

README Footer Beacon