Deploy OneAgent using AWS Elastic Beanstalk

AWS Elastic Beanstalk is a service provided by Amazon Web Services that gives you the option of deploying and auto-scaling applications and services. You can modify your deployment by supplying additional resources or packages using a predefined .ebextensions directory zipped into your deployment package. For more information, see the AWS documentation.

You can prepare configurations where Dynatrace OneAgent is already part of your application deployment. In such cases you won't have to manually install OneAgent or restart servers to enable service monitoring.

What you need

  • Dynatrace OneAgent download link (Windows or Linux).
  • Access to your AWS Console.

Get the Dynatrace OneAgent download

See the section on downloading the Dynatrace OneAgent installer for specific instructions on downloading Dynatrace OneAgent for installation with Elastic Beanstalk.

Create a configuration to install Dynatrace OneAgent

Because the specifics of this type of installation depend heavily on user customizations, we can't provide a simple set of steps that will work in all scenarios. Following is only a brief overview of the entire process, with examples that will help you create your own deployment.

Customizing your installation

When creating the configuration file, you can customize your installation using all the supported Dynatrace OneAgent installation parameters. In the examples below, we used the APP_LOG_CONTENT_ACCESS=1 parameter enabling Dynatrace OneAgent to access log files for the purpose of Log Monitoring. If you want to add more parameters, separate them with a space. Learn more about Windows installation parameters and Linux installation parameters.

It's best to split plugin configuration into two files, one for downloading the Dynatrace OneAgent installer and a second for invoking the installation and post-installation tasks. Note that the Elastic Beanstalk plugin script file names are important—the Amazon interpreter executes these in alphabetical order.

Create the download configuration file and save it with the name 0dynatraceDownload.config. The configuration file needs to contain a files section where you must define:

  • Download path and target file name, for example /tmp/
  • Proper user rights settings
  • The Dynatrace OneAgent download URL you copied to your text editor.

For example:

      mode: "000755"
      owner: root
      group: root
      source: ""

Create a file called 1dynatraceInstallAndPost.config to execute the Dynatrace OneAgent installer and perform other tasks, such as service restart.
The following script checks for an existing Dynatrace OneAgent setup, executes installation from the /tmp directory if no OneAgent is found, the file is passing the APP_LOG_CONTENT_ACCESS=1 installation parameter enabling Log Monitoring and restarts the httpd service:

    command: "[ -d /opt/dynatrace/oneagent ] || /tmp/ APP_LOG_CONTENT_ACCESS=1"
    cwd: /tmp
      command: service httpd restart

Copy the 0dynatraceDownload.config and 1dynatraceInstallAndPost.config files to the .ebextensions directory and place it in the Beanstalk deployment package.

Extend your configuration

For convenience, you can also include steps to download Dynatrace OneAgent in your configuration.

This Linux script example includes the Dynatrace OneAgent download in the configuration. While this is necessary for the first installation of Dynatrace OneAgent, this may substantially extend future application updates, because you download Dynatrace OneAgent each time.

You can improve your Beanstalk configuration by adding a check for an existing Dynatrace OneAgent installation and have your scripts download Dynatrace OneAgent only when it isn't found on the system.

Look at the following Linux configurations example carefully before creating your own scripts. Take care in formatting and escaping special characters. The Amazon interpreter is sensitive to syntax errors.

    mode: "000755"
    owner: root
    group: root
    content: |
      if [ ! -d /opt/dynatrace/oneagent ]; then
        wget -O /tmp/ ""
        chmod 755 /tmp/
        sudo chown root:root /tmp/
        sudo /tmp/

    command: /tmp/ APP_LOG_CONTENT_ACCESS=1
    command: service nginx restart
    ignoreErrors: true