AWS and AppDynamics APM

[Monitoring Cloud Applications]

Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


To deploy applications with Elastic Beanstalk, you need to know the variable settings for every AppDynamics Agent your application needs. This tutorial uses the Java Agent only, which keeps the list of required settings smallshort.

In a text editor, create a string that begins with ./


Script optionEnvironment variableNotes
  • Fully-qualified domain name for the AppDynamics Controller with which you intend to monitor your application
  • Primary port used by the monitoring AppDynamics Controller
  • Default is 8090
  • the Controller under Settings > License > Account


  • Include only if your Controller has Analytics
  • Tells the Analytics plugin the target URL for the Events Service
  • The Analytics plugin sends data to the Events Service, not the Controller


  • Include only if your Controller has Analytics
  • In the Controller under Settings > License > Account


  • Must be the code for the region shown in your AWS console.
  • For example, if the console shows Ohio, the code is us-east-2


  • Name of your choice for the example application
  • Name of your choice, for the new environment that the script creates


  • Specifies where on the local filesystem the script should copy the Sample App, after cloning it from GitHub


  • Include only if you want to use eb ssh 
  • eb ssh allows you to log into the EC2 instance on which the script deploys the app
  • For the value, use the name of your chosen Key Pair
  • Optional—if not specified, AWS uses a default
  • Must be t2.small or larger for this demo to run properly

The simplest possible ./ command (no Analytics, no Server Visibility, no SSH) might look something like this: