Start Your Engines !

image

You must have enough available VPCs, Elastic IPs, and NAT Gatweways in the region you are working in to successfully create an EKS Cluster with a managed node group of 2 nodes. You also need to have space for three S3 Buckets. If you run into a problem during the setup, it is usually associated with insufficient resources or permissions in your AWS account. You can resolve resource constraints by requesting a quota increase for your AWS account.

In order to prevent charges to your AWS account, we recommend cleaning up the infrastructure that gets created with the setup utility. If you plan to keep things running so you can examine the workshop a bit more, please remember to do the cleanup when you are done. It is very easy to leave things running in an AWS account, forget about it, and then accrue charges.

Just so you understand ahead of time, you can easily clean up all the resources that get created by the setup utility by using the commands below:

cd /home/ec2-user/environment

./teardownWorkshop.sh 

Let’s do this !


Now that you’ve got all the prerequisites out of the way, you can kick off the final setup steps and go grab a cup of coffee while the setup utility does the rest.

Ensure you are in your home directory by executing the command below:

cd /home/ec2-user/environment

Download the setup script using the following command:

curl --silent -L https://raw.githubusercontent.com/Appdynamics/appd_aws_observability_lab/main/setupWorkshop.sh -o ./setupWorkshop.sh

Use the following command to make the script executable:

chmod +x setupWorkshop.sh

Use five (5) letters of your first, and or, your last name to create your unique workshop user name using the command below:

EXAMPLE:  export appd_workshop_user=TOMSM

export appd_workshop_user=<YOUR USER NAME>

Use the command below to execute the setup script::

./setupWorkshop.sh

The setup utility takes approximately 28 minutes to complete. While you’re waiting for the setup to finish you can go to the AppDynamics Advantage section where you can find out why AD Financial selected AppDynamics as their preferred observability solution.

The output from the setup script when the EKS cluster is created, should look like this:

EKS cluster creation as part of the complete setup, takes approximately 15 minutes of the total time.

image

The output from the setup script when it ends, should look like this:

image

What the setup utility does

image

01) Installs Java JDK 1.8

02) Resizes the Disk on your C9 instance

03) Installs kubectl

04) Installs eksctl

05) Installs docker-compose

06) Installs the AppDynamics Database agent

07) Creates an EC2 security group for extenal access to RDS Databases

08) Creates RDS databases with the security group attached

09) Creates three S3 buckets

10) Creates two Application Performance Monitoring apps in the AppDynamics Controller

11) Creates two Browser Real User Monitoring apps in the AppDynamics Controller

12) Creates two AppDynamics Database collectors in the AppDynamics Controller

13) Creates an RBAC User in the AppDynamics Controller

14) Creates an RBAC Role in the AppDynamics Controller

15) Adds the RBAC User in the AppDynamics Controller to the appropriate RBAC Roles

16) Creates the EKS Cluster

17) Deploys the Post-Modernization application to the EKS Cluster

18) Waits for the application to initialize in the EKS Cluster

19) Deploys the AppDynamics Machine agent to the EKS Cluster

20) Deploys the AppDynamics Cluster agent to EKS Cluster

21) Exposes the website front end with an ELB in the EKS Cluster

22) Deploys the Pre-Modernization application to your local C9 instance

23) Creates the teardwown file

Using a shell script -

Using the AWS Java SDK -

Using the AppDynamics REST API -


Next

While you are waiting for the setup utility to finish, go to the AppDynamics Advantage section where you can find out why AD Financial selected AppDynamics as their preferred observability solution.