The transition to distributed applications is in full swing, driven mainly by our need to be “always-on” as consumers and fast-paced businesses. That need is driving deployments to have more complex requirements along with the ability to be globally diverse and rapidly innovate.
Cloud is becoming the de facto deployment option for today’s applications. Many cloud deployments choose to host their applications on AWS for the globally diverse set of regions it covers and the myriad of services (for faster development and innovation) available, as well as to drive operational and capital costs down. On AWS, development teams are finding additional value in migrating to Kubernetes on Amazon EKS, testing out the latest serverless options, and improving traditional, tiered applications with better services.
Elastic Observability offers 30 out-of-the-box integrations for AWS services with more to come.
A quick review highlighting some of the integrations and capabilities can be found in a previous post:
Some additional posts on key AWS service integrations on Elastic are:
A full list of AWS integrations can be found in Elastic’s online documentation:
In addition to our native AWS integrations, Elastic Observability aggregates not only logs but also metrics for AWS services and the applications running on AWS compute services (EC2, Lambda, EKS/ECS/Fargate). All this data can be analyzed visually and more intuitively using Elastic’s advanced machine learning capabilities, which help detect performance issues and surface root causes before end users are affected.
For more details on how Elastic Observability provides application performance monitoring (APM) capabilities such as service maps, tracing, dependencies, and ML based metrics correlations:
That’s right, Elastic offers metrics ingest, aggregation, and analysis for AWS services and applications on AWS compute services (EC2, Lambda, EKS/ECS/Fargate). Elastic is more than logs — it offers a unified observability solution for AWS environments.
In this blog, I’ll review how Elastic Observability can monitor metrics for a simple AWS application running on AWS services which include:
- AWS EC2
- AWS ELB
- AWS RDS (AuroraDB)
- AWS NAT Gateways
As you will see, once the integration is installed, metrics will arrive instantly and you can immediately start reviewing metrics.
Prerequisites and config
If you plan on following this blog, here are some of the components and details we used to set up this demonstration:
Three tier application overview
Before we dive into the Elastic configuration, let’s review what we are monitoring. If you follow the instructions for aws-three-tier-web-architecture-workshop, you will have the following deployed.