Monitor AWS Elastic Beanstalk

To install OneAgent, you need two configuration files:

• One file for downloading the OneAgent installer
• Another file for invoking the installation and post-installation tasks.

1. In the Beanstalk deployment package, create a .ebextensions directory. The two configuration files mentioned above must be placed in this directory.

2. Create a configuration file for downloading the installer named 0dynatraceDownload.config.

   The file must contain a files section that defines:

   • The download path and target file name (for example, /tmp/dynatraceinstall.sh)
   • Proper user rights settings
   • The OneAgent download URL mentioned in the prerequisites.

   Example:

   yamlcopydownload
   files:
       "/tmp/dynatraceinstall.sh":
         mode: "000755"
         owner: root
         group: root
         source: "https://abcdefghij.live.dynatrace.com/api/v1/deployment/installer/agent/unix/default/latest?arch=x86&flavor=default&Api-Token=abcdefghijklmnopqrstu"

   Note: Make sure to replace the generic values in the example above with your own.

3. Create a file to execute the OneAgent installer and perform other tasks such as service restart, named 1dynatraceInstallAndPost.config.

   In the example below, the script checks for an existing OneAgent setup and, if no OneAgent is found, executes the installation from the /tmp directory, setting the --set-proxy=172.1.1.128:8080 installation parameter to connect the agent to a specific proxy. Then the httpd service is restarted.

   yamlcopydownload
   commands:
     install_dynatrace:
       cwd: /tmp
       command: "/bin/sh dynatraceinstall.sh --set-proxy=172.1.1.128:8080"
     restart_httpd:
       command: "service httpd restart"

   If you want to add more parameters, separate them with spaces. To learn more about installation parameters, see how to customize OneAgent installation on Linux.

   Do not use the command's env property because it overwrites, rather than appends, the existing environment and will cause OneAgent installation to fail.

4. optional Extend your configuration.

   You can also include steps to download OneAgent in your configuration.

   The example below includes OneAgent download in the configuration. While this is necessary for the first installation of OneAgent, it might substantially lengthen future application updates because you download OneAgent each time you run the script. To improve your Beanstalk configuration, add a check for an existing OneAgent installation and have your scripts download OneAgent only when it isn't found on the system.

   Note: Inspect the following Linux configuration example carefully before creating your own scripts. The Amazon interpreter is sensitive to syntax errors. Take care in formatting and escaping special characters.

   yamlcopydownload
   files:
     "/tmp/dynatraceinstall.sh":
       mode: "000755"
       owner: root
       group: root
       content: |
         #!/bin/bash
         if [ ! -d /opt/dynatrace/oneagent ]; then
           wget -O /tmp/Dynatrace-OneAgent.sh "https://abcdefghij.live.dynatrace.com/api/v1/deployment/installer/agent/unix/default/latest?arch=x86&flavor=default&Api-Token=abcdefghijklmnopqrstu"
           chmod 755 /tmp/Dynatrace-OneAgent.sh
           sudo chown root:root /tmp/Dynatrace-OneAgent.sh
           sudo /tmp/Dynatrace-OneAgent.sh
         fi
   
   commands:
     install_dynatrace:
       cwd: /tmp
       command: "/bin/sh dynatraceinstall.sh --set-proxy=172.1.1.128:8080"
     restart_nginx:
       command: service nginx restart
       ignoreErrors: true

To install OneAgent, you need two configuration files:

• One file for downloading the OneAgent installer
• Another file for invoking the installation and post-installation tasks.

1. Create a configuration file for downloading the installer named 0dynatraceDownload.config.

   The file must contain a sources section that defines:

   • The download destination (for example, your desktop)
   • The OneAgent download URL mentioned in the prerequisites.

   Example:

   yamlcopydownload
   files:
       "C:/OneAgent/Dynatrace-OneAgent-Installer.exe":
           source: "https://abcdefghij.live.dynatrace.com/api/v1/deployment/installer/agent/windows/default-unattended/latest?Api-Token=abcdefghijklmnopqrstu&arch=x86&flavor=default"

   Note: Make sure to replace the generic values in the example above with your own.

2. Create a file to execute the OneAgent installer and perform other tasks such as service restart, named 1dynatraceInstallAndPost.config.

   The file must contain a commands section that defines the installation command for OneAgent.

   Do not use the command's env property because it overwrites, rather than appends, the existing environment and will cause OneAgent installation to fail.

   In the example below, the script executes the installer from the administrator's desktop folder in quiet mode (no graphical user interface involved). The file passes the --set-proxy=172.1.1.128:8080 installation parameter to connect the agent to a specific proxy.

   yamlcopydownload
   commands:
       install_oneagent:
           command: "C:/OneAgent/Dynatrace-OneAgent-Installer.exe --quiet --set-proxy=172.1.1.128:8080"

   If you want to add more parameters, separate them with with spaces. To learn more about installation parameters, see how to customize OneAgent installation on Windows.

   You don't need to add extra commands following OneAgent installation. Amazon will restart IIS on its own after you've successfully uploaded all your application files.