For a no container setup, install the Datadog Agent in Elastic Beanstalk using Advanced Environment Customization with Configuration Files (.ebextensions):

1. Create a folder named .ebextensions in the root of your application source bundle.
2. Download 99datadog.config and put it in the .ebextensions folder.
3. Change the value of api_key within the file template for /etc/datadog-agent/datadog.yaml with your Datadog API Key.
4. Change the value of site in /etc/datadog-agent/datadog.yaml to your Datadog region (for example: ) to ensure the Agent sends data to the right Datadog location.
5. Pin a specific Agent version by setting DD_AGENT_VERSION under option_settings to ensure that all hosts run the same version of the Agent.
6. Deploy your application with the Elastic Beanstalk Console, EB CLI, or AWS CLI.

You can add additional Agent settings to /etc/datadog-agent/datadog.yaml.

For example, to enable Live Process Monitoring:

process_config:
  enabled: "true"

Trace collection

When the application isn’t containerized and the Datadog Agent is configured with 99datadog.config, tracing is enabled without any additional configuration, provided the application is instrumented with the tracing library setup.

For a no container setup, install the Datadog Agent in Elastic Beanstalk using Advanced Environment Customization with Configuration Files (.ebextensions):

1. Create a folder named .ebextensions in the root of your application source bundle.
2. Download 99datadog-windows.config and move it to the .ebextensions folder.
3. In 99datadog-windows.config, replace the APIKEY value with your Datadog API Key.
4. (Optional) The 99datadog-windows.config file adds the .NET APM Tracing Library to generate traces. If you don’t want to enable APM in your environment, remove the packages section, the 02_setup-APM1 section, and the 03_setup-APM2 section.
5. (Optional) If you need to add environment variables, set them in the 00_setup-env1 section of 99datadog-windows.config. You can remove this section if you do not need to set environment variables.
6. Deploy your application with the Elastic Beanstalk Console, EB CLI, or AWS CLI.

Trace collection

When the application isn’t containerized and the Datadog Agent is configured with 99datadog-windows.config, tracing is enabled without any additional configuration. For more information on instrumenting tracing, see Set up Datadog APM.

For a single Docker container setup, install the Datadog Agent in Elastic Beanstalk using Advanced Environment Customization with Configuration Files (.ebextensions).

Note: This setup requires your API key to be placed in the .ebextensions directory, which is part of the source code. Use AWS Secret Manager or other secret management tooling to protect your API key.

1. Create a folder named .ebextensions in the root of your application source bundle.
2. Download 99datadog.config and put it in the .ebextensions folder.
3. Change the value of api_key within the file template for /etc/datadog-agent/datadog.yaml with your Datadog API Key.
4. Change the value of site in /etc/datadog-agent/datadog.yaml to your Datadog region (for example: ) to ensure the Agent sends data to the right Datadog location.
5. Pin a specific Agent version by setting DD_AGENT_VERSION under option_settings to ensure that all hosts run the same version of the Agent.
6. Deploy your application with the Elastic Beanstalk Console, EB CLI, or AWS CLI.

You can add additional Agent settings to /etc/datadog-agent/datadog.yaml.

For example, to enable Live Process Monitoring:

process_config:
  enabled: "true"

Trace collection

To enable tracing for single Docker containers:

1. Update the /etc/datadog-agent/datadog.yaml section in the 99datadog.config file with apm_non_local_traffic, formatted like this:

   apm_config:
     enabled: "true"
     apm_non_local_traffic: "true"
   

2. Set up the tracing libraries to direct traces to the Gateway IP of the bridge network, which defaults to 172.17.0.1 from inside the application container. (If you’re not sure this is the Gateway IP, run docker inspect <container id> to confirm.)

For all languages, set the environment variable DD_AGENT_HOST to the Gateway IP. Alternatively, for the languages below, set the host name programmatically using:

Python

from ddtrace import tracer

tracer.configure(hostname="172.17.0.1")

Node.js

const tracer = require('dd-trace');

tracer.init({ hostname: "172.17.0.1" });

Ruby

require 'ddtrace'

Datadog.configure do |c|
  c.tracer hostname: "172.17.0.1")
end

Go

package main

import (
    "gopkg.in/DataDog/dd-trace-go.v1/ddtrace/tracer"
)

func main() {
  tracer.Start(tracer.WithAgentAddr("172.17.0.1"))
  defer tracer.Stop()

  // ...
}

For multiple Docker containers, use the containerized Datadog Agent to monitor Docker usage with a file named Dockerrun.aws.json.

A Dockerrun.aws.json file is an Elastic Beanstalk—specific JSON file that describes how to deploy a set of Docker containers as an Elastic Beanstalk application. You can use this file for a multicontainer Docker environment. Dockerrun.aws.json describes the containers to deploy to each container instance in the environment and the data volumes to create on the host instance for the containers to mount.

A Dockerrun.aws.json file can be used on its own or zipped up with additional source code in a single archive. Source code that is archived with Dockerrun.aws.json is deployed to container instances and accessible in the /var/app/current/ directory. Use the volumes section of the config to provide mount points for the containers running on the instance and the mountPoints section of the embedded container definitions to mount them from the containers.

The following code sample illustrates a Dockerrun.aws.json declaring the Datadog Agent. Update the containerDefinitions section with your Datadog API Key, tags (optional), and any additional container definitions. If needed, this file can be zipped with additional content as described above. For more info about the syntax of this file, see Multicontainer Docker configuration.

Notes:

• For high resource usage, you may need a higher memory limit.
• To ensure all hosts run the same Agent version, it is recommended to change agent:7 to a specific minor version of the Docker image.

{
    "AWSEBDockerrunVersion": 2,
    "volumes": [
        {
            "name": "docker_sock",
            "host": {
                "sourcePath": "/var/run/docker.sock"
            }
        },
        {
            "name": "proc",
            "host": {
                "sourcePath": "/proc/"
            }
        },
        {
            "name": "cgroup",
            "host": {
                "sourcePath": "/cgroup/"
            }
        }
    ],
    "containerDefinitions": [
        {
            "name": "dd-agent",
            "image": "gcr.io/datadoghq/agent:7",
            "environment": [
                {
                    "name": "DD_API_KEY",
                    "value": "<YOUR_DD_API_KEY>"
                },
                {
                    "name": "DD_SITE",
                    "value": "<YOUR_DD_SITE>"
                },
                {
                    "name": "DD_TAGS",
                    "value": "<SIMPLE_TAG>, <KEY:VALUE_TAG>"
                }
            ],
            "memory": 256,
            "mountPoints": [
                {
                    "sourceVolume": "docker_sock",
                    "containerPath": "/var/run/docker.sock",
                    "readOnly": false
                },
                {
                    "sourceVolume": "proc",
                    "containerPath": "/host/proc",
                    "readOnly": true
                },
                {
                    "sourceVolume": "cgroup",
                    "containerPath": "/host/sys/fs/cgroup",
                    "readOnly": true
                }
            ]
        }
    ]
}

Creating the environment

Once the container definition is ready, ship it to Elastic Beanstalk. For specific instructions, see Multicontainer Docker Environments in the AWS Elastic Beanstalk documentation.

DogStatsD

To collect custom metrics from your application container using DogStatsD in the Multicontainer Docker Environment, add the following to your Dockerrun.aws.json:

1. Add the environment variable DD_DOGSTATSD_NON_LOCAL_TRAFFIC under the dd-agent container:

   {
     "name": "DD_DOGSTATSD_NON_LOCAL_TRAFFIC",
     "value": "true"
   }
   

2. Add a link to the dd-agent container under your application container:

   "links": [ "dd-agent:dd-agent"]
   

See DogStatsD and Docker for additional information.