[Monitoring Cloud Applications]
On this page:
This page helps you map out your cloud application architecture by choosing particular AWS (or other) services for your cloud application architecture.
In so doing, you make tradeoffs: between convenience and flexibility, between resiliency and simplicity, and others. Be sure that these choices are solidly based on your project's needs. That way you avoid risky or costly situations, for example where the application needs to scale up or down but cannot.
Complete the process below to ensure that sound, well-informed choices go into your architecture. Next, you can learn about monitoring applications deployed with Elastic Container Service (ECS). If you want to use a combination of AWS services not covered in these pages, contact your AppDynamics representative.
Be aware of the way AWS terms map to AppDynamics terms, as shown in the table below.
|container (in task instance)||AppDynamics Container|
|EC2 instance private IP||AppDynamics Host ID|
To begin creating your cloud application architecture, identify which tiers your application must provide.
One common architecture comprises these three services, each of which is a tier in AppDynamics terms:
Decide whether your cloud application architecture requires one or more of these tiers, or different ones.
To these, add one more service which is not considered a tier: a Java server to run the AppDynamics Controller.
In AWS, you can deploy applications
Another option, "serverless" cloud deployment, is mostly beyond the scope of this documentation.
Consider how your application needs to scale. Docker or Kubernetes containers may provide faster, more reliable scaling than deploying directly onto EC2 instances—but the latter option is simpler. Blogs and conference presentations like this one from Amazon explain the tradeoffs.
Decide whether your architecture should use containers, and if so, what kind.
AWS offers more than choice for particular functions. For example, you can use either ECS or Elastic Beanstalk for orchestration—each offers a different balance between simplicity and flexibility.
Some basic choices are outlined below.
The AWS Elastic Load Balancer products are
If you use containers, you must decide how to distribute each service's containers across the EC2 hosts. There are two possibilities:
For ECS, Amazon recommends the second approach as a best practice. ECS scales applications much more efficiently with homogeneous EC2 hosts than with heterogeneous ones.
In the case of an architecture built with Docker containers, EC2 hosts, and ECS orchestration, we would describe the results like this:
The Machine Agent pulls metrics for