[Monitoring Cloud Applications]
Although the architecture for this example is trivially simple, much more is possible with Elastic Beanstalk.
After completing you complete this demo, the next step is to deploy manually rather than running the script. See Deploying applications manually.
In the AWC console:
If you want to SSH into EC2 instances:
To deploy applications with Elastic Beanstalk, you need to know the variables variable settings for every AppDynamics Agent your application needs. This tutorial uses the Java Agent only, which keeps the list of variables required settings small.
In a text editor, create a string that begins with with
To that string, add script options, paired with values for the corresponding environment variables, as shown Append the script options and environment variable settings to the command string, as described in the table below. See the example command string below the table.
The completed string is your
./test.sh -c master-saas-controller.example.com -p 8090 -K <your-secret-key> -r us-east-2 -a tutorialapp -e tutorialenv -b /Users/exampleperson/aws-elasticbeanstalk/java -i t2.small
Do not use the procedure as described here,
with your secret key
entered at the command line in plain text,
in a production environment.
It may or may not be considered acceptable even for testing, depending on practices at your organization.
All file paths in these examples begin with the home directory, designated by the ~ character. Replace the ~ with whatever filesystem location you prefer.
In a terminal:
cdinto the tutorial target directory as described above.
In a terminal, still in the tutorial target directory.